https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88568
--- Comment #20 from Jakub Jelinek <jakub at gcc dot gnu.org> --- (In reply to Stephen Kitt from comment #19) > (In reply to Jakub Jelinek from comment #18) > > (In reply to Stephen Kitt from comment #17) > > > jon_y, you can have your weekend back ;-). > > > > Well, it should be tested also with a GCC bootstrap/regtest, that is a usual > > procedure for testing GCC changes. > > Ah, right, of course. I’ve run a cross-bootstrap, but not a bootstrap on > Windows, nor have I run the test suite on Windows. Cross compilers don't bootstrap (build themselves multiple times), only build. Sure, I have built a cross compiler to write and verify this change too, but I have no access to Windows to bootstrap/regtest it natively. As I said on gcc-patches, it is highly unlikely it will regress something, because if it doesn't crash in the newly added condition, then it partially reverts to the January state.
