The patch that introduced the bug is at [1]. Does it look to you like it introduced a bug? Granted, you're not a gcc developer—neither am I—but the gcc develo

The patch that introduced the bug is at [1]. Does it look to you like it introduced a bug? Granted, you're not a gcc developer—neither am I—but the gcc developers didn't think so either. Bugs are accidentally introduced all the time, true. But I don't think it's fair to say that this is a ridiculous line of reasoning. 1. https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=14b7950f126f84fa585e3a057940ff10d4c5b3f8;hp=1b1e13dbde7f3eef0f8356af05c5de1fb46cb31b https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=14b7950f12...