https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94506
Jakub Jelinek <jakub at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jakub at gcc dot gnu.org
--- Comment #2 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Yeah, when you have the two GCC revisions, I'd suggest to save object files
from both builds and do a binary search during linking on which object file
matters (start with half *.o files built by one gcc revision and half with the
other one etc.).
Once you have (hopefully) single TU where kernel works if everything is built
by newer gcc but that single one by older gcc and doesn't work if everything is
built by older gcc but that single one by newer gcc, attach the preprocessed
source for it, both assembler outputs and say exact gcc command line.
Depending on the amount of changes in the file, we might need further bisection
using debug counters or something similar.
As Richard said, the patch fixed heuristics, so it is unlikely the bug is in
that exact change, but can be anywhere else (could be on the kernel side too).
