https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114288
--- Comment #11 from Jeffrey A. Law <law at gcc dot gnu.org> --- The larger point is we don't just disable passes because they have a bug, or even multiple bugs. We need to do the right thing from an engineering standpoint, ie, actually debug the problem. In fact, this is a great example of why disabling would be a mistake. This bug is going to be easier to analyze than the python issue triggered by f-m-o or the m68k bootstrap issue. Had we disabled, we likely wouldn't have tripped over this issue.
