-
Notifications
You must be signed in to change notification settings - Fork 260
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error compiling xtensor tests with latest xsimd on MSVC 2019 v16.11.5 #625
Comments
Same here. Does this only happen for the latest vs2019 version (v16.11.5)? |
I did not try older Visual Studio with latest xsimd. I can only say that older xsimd (<= 7.x) used to work. |
Kindly pinging on this issue again. This is currently blocking us from moving to xsimd 8.x series (and in turn blocking the latest xtensor and xtensor-python, oh my). |
I have a small reproducer here: https://godbolt.org/z/fdeGnzWEa basically the type parameter of the batch doesn't look like a supported scalar type (It's a chrono time_point). I can improve the error message, but that's probably not what you expect. My understanding is that this comes from xtensor, @JohanMabille any hint? |
Thanks a lot for the PR, I think it looks good. But I can not test it easily right now because our Windows build is currently being upgraded to VS2022. It may take a few days before I get back to this, is it ok? |
I can reproduce the bug on a local Windows machine, now investigating it, but that looks like a compiler bug that will require some cargo kulting workaround :/ |
I see, very annoying... if its really a compiler bug then maybe I can try with Visual Studio 2022. If its fixed there then I'm fine, we can always flee forward... |
I tried in the CI with VS 2022, same issue. |
same here with VS2022. I have to remove xtensor::use_simd to compile successfully. |
Maybe it is related with this issue xtensor-stack/xtensor#2736 |
I get a number of errors when building latest xtensor tests against xsimd 8.0.3 on MSVC with latest Visual Studio v16.11.5. The problem is here reported for test_xdatesupport, but appears in other sources too.
The error is
The text was updated successfully, but these errors were encountered: