https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77966
--- Comment #7 from Martin Liška ---
Yes, the reason is that aggressive loop optimizations are disabled if a
-fsanitize is enabled.
If you want to catch the out of bounds access to wq_lock array, you can use
-fsanitize=undefined.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77966
--- Comment #6 from Josh Poimboeuf ---
(In reply to Arnd Bergmann from comment #5)
> I checked the test case using "-fsanitize=unreachable" and that avoids the
> problem.
>
> Josh, should we set that whenever we enable objtool in the kernel?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77966
--- Comment #5 from Arnd Bergmann ---
I checked the test case using "-fsanitize=unreachable" and that avoids the
problem.
Josh, should we set that whenever we enable objtool in the kernel?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77966
--- Comment #4 from Denis Vlasenko ---
This confuses object code sanity analysis tools which check that every function
ends "properly", i.e. with a return or jump (possibly padded with nops).
Can gcc get an option like
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77966
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
