https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61047
--- Comment #24 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- > I agree that this is too risky to backport, but I disagree with the decision > not to fix it on the trunk. We have plenty of time to watch for performance > regressions and/or bugs it introduces there, and even if this bug is only > hit by machine generated code, it would be helpful to all the people that > try to report bugs against gcc if they wouldn't have to analyze and then > ignore similar cases every few days because we chose to never fix it on the > gcc side. As far as I know "all the people" is just one guy submitting machine-generated testcases and repeatedly running into the issue. I suspended the PR because nobody else reported it, in particular on real-life software. IMO there are far more pressing issues to be addressed than this one. That being said, if you feel strongly about it, then go ahead, I won't oppose.
