Open emmenlau opened 3 years ago
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?
@emmenlau can you confirm that with https://github.com/xtensor-stack/xsimd/pull/665 you at least get a decent error message?
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. Wondering how the performance will degrade without xsimd.
Maybe it is related with this issue https://github.com/xtensor-stack/xtensor/issues/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