https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66780
--- Comment #2 from John Paul Adrian Glaubitz <glaubitz at physik dot fu-berlin.de> --- (In reply to Kazumoto Kojima from comment #1) > It turned out that the fix for PR65249 causes this problem. > The codes for stack protect can be inserted after some function > call returning a value. That return value in R0 register could > be clobbered with the fix for PR65249. Interesting. Could this also be the cause for PR66312 and PR66563 after all? Both actually occurred only after the patch for PR65249 was merged. In PR65979 (comment 8) [1], we already speculated which recent change introduced the issue and I'd bet that the wrong code generated here is responsible for the aforementioned issues as well as the weird behavior I have observed with grep [2] as well. > I think that the wrong code is worse than the ICE. I'd like > to revert the patches of PR65249 and reopen that PR. I agree. Please revert this fix as soon as possible as currently almost all packages fail to build as Debian enables -fstack-protector-strong by default. Adrian > [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65979#c8 > [2] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66563#c46
