https://gcc.gnu.org/bugzilla/show_bug.cgi?id=121432
--- Comment #3 from Sam James <sjames at gcc dot gnu.org> --- (In reply to Thomas Petazzoni from comment #0) > However, at this point we are a bit clueless on how to move forward with the > investigation. The issue is reproducible in Qemu, which we are using for > testing. Let us know what additional details would be useful to help > investigate this issue. A list: * Compressed binaries of the kernel before and after the commit * Take the build tree of the kernel with gcc-good, and gcc-bad (where it's one commit before and then the bad commit) and copy objects from the gcc-bad tree into the gcc-commit tree, re-running make repeatedly, until you find which the bad object is (if no LTO is involved, it has to be one object) * Once you have that object, we'll need preprocessed source corresponding to it (but we'll worry about that when you get there)
