-
Notifications
You must be signed in to change notification settings - Fork 2
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
Compilation error with MSVC #10
Comments
I have never found time to test vir-simd with MSVC. So yes, I'm sure there are bugs. At the very least the You're right about the README. I added several features that make use of concepts. Needs to be documented. I'll take a look at the Conan PR. I was independently also looking into creating a Conan package. But thank you for beating me there! 😉 |
See #11, better? |
Yes, thanks! |
Sorry for skipping the According to https://learn.microsoft.com/en-us/cpp/preprocessor/predefined-macros?view=msvc-170 vir-simd should test if _MSVC_LANG is defined, and if yes use that instead of __cplusplus. |
Fixes: #10 ChangeLog: * vir/simd.h: Prefer _MSVC_LANG over __cplusplus.
Fixes: #10 ChangeLog: * vir/simd.h: Prefer _MSVC_LANG over __cplusplus.
Fixes: #10 ChangeLog: * vir/simd.h: Prefer _MSVC_LANG over __cplusplus.
Hi! I was trying to add vir-simd to Conan Center PR but the CI fails with MSVC when checking for C++17.
It seems that the
__cplusplus
macro contains a wrong value unless we specify de/Zc:__cplusplus
compiler flag. It would be easy to add that flag for the package test but that would require every user of the library to set that flag. Maybe that's what you wanted or maybe that check could be defined using the MSVC macro_MSC_VER
. I'm assuming MSVC support, if that is not the case please let me know and I'll update the Conan PR accordingly.I also spent some time trying to make
iota_v
work until I saw that it is only available with C++20. I think that should be in the README.I apologize I'm only complaining 😅 . I'll try to create a PR at least for the iota issue.
The text was updated successfully, but these errors were encountered: