https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72785
ktkachov at gcc dot gnu.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|INVALID |---
--- Comment #24 from ktkachov at gcc dot gnu.org ---
I still see this when building an allmodconfig 4.9 Linux kernel for aarch64
(arm64 in kernel-speak).
Just do:
<Set CROSS_COMPILE to the aarch64 toolchain>
make ARCH=arm64 allmodconfig
make ARCH=arm64 -j<n>
Does anyone know of a kernel patch in flight to fix this in the kernel?
If not, should GCC work around this somehow? (perhaps by making jump-threading
less aggressive when __builtin_constant_p is involved?)
