-
Notifications
You must be signed in to change notification settings - Fork 295
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
HwyMathTestGroup/HwyMathTest.TestAllAtan2/NEON_WITHOUT_AES # GetParam() = 536870912 (Subprocess aborted) #1549
Comments
|
gcc-12:
|
@jan-wassenberg could you remind me how I can refactor the I always find it confusing the lines:
In my case I know I need to compile only against |
I appreciate you taking the time to raise the issues! So it seems gcc-13 only, gcc-12 is fine. I wasn't able to repro with gcc-12 either. Here is the full version with dynamic dispatch: https://gcc.godbolt.org/z/bvMEhnxzK Hope this helps :) |
I did click on the link. I failed to understand how that could compile (automated default to EMU128 when not specified?) GCC dev expect bug reporter to produce a reduce test case. Last time I manually extracted the math function into a smaller test case I could not reproduce the issue. I really need to use |
Ah, on aarch64 we always have NEON (without AES) so no flag required :) In case the link is behaving strangely, here is the start of the file. Note that the math-inl header includes highway.h.
|
IsInf depends on signed integer being wrapping incorrectly.
So not depending on signed integers here and use unsigned types which are defined to be wrapping. |
Thank you @malaterre for sending the patch, and @pinskia for investigating and commenting here :) I had thought that signed overflow/underflow was fine for vector (but not scalar) code, also because we do test with ubsan. Good to know that this isn't checking vector code. After this patch lands, I will update the other IsInf as well, and look for MSB/Clear for similar occurrences. |
[sorry for the flood of issues]
Thsi is to track test failure:
The text was updated successfully, but these errors were encountered: