-
Notifications
You must be signed in to change notification settings - Fork 252
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
Build failure on ARM v8 with SVE (neoverse_v1
) architecture
#1005
Comments
neoverser_v1
) architectureneoverse_v1
) architecture
Thanks for the bug report! Can you share a minimal c++ input that fails? |
Thanks for the fast response. I'd love to provide a minimal c++ input, maybe you can help me create one since I'm unfamiliar with Regarding the |
This looks like the right reproducer: https://godbolt.org/z/E4KxKqcMP |
Good thinking on using godbolt for this, that was much quicker than going back and forth with me trying out a compilation natively :) Thanks for investigating this and the quick fix! |
Environment
12.1.1
Error
I'm running into a build issue when compiling code that uses
xsimd
:The same code, with the same compiler flags / compiler version builds fine on Neoverse N1 (and on zen2, zen3, haswell and skylake by the way).
I've tried to dig into the code of
xsimd
a bit, but in the above error I'm in a bit over my head when it comes to all the types flying around :) Hoping that someone with more expertise inxsimd
spots where this might be going wrong... My bet is there was some change in terms of datatypes, intrinsics, or similar in Neoverse V1 that was not accounted for (yet) inxsimd
that makes this go wrong compared to e.g. Neoverse N1.Not sure if this might be useful, but to get an overview of the supported instructions on N1 vs V1, on Neoverse N1:
And for Neoverse V1:
N.B. Note that this none of these codes is mine: I'm just the guy having the pleasure of trying to build them on different hardware architectures :)
The text was updated successfully, but these errors were encountered: