https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87252
--- Comment #10 from Hans-Peter Nilsson <hp at gcc dot gnu.org> --- (In reply to Abrahm Scully from comment #9) > Either way, building gcc-4.7.4 first and then building gcc-10 with that > produces a compiler without the problem. > > Again, sorry for the noise. Please, do *not* apologize. Even if you'd just repeat other observations, your observations would serve as a confirmation. But they're also new AFAICT. So, your recent observation is that gcc-4.7.4 apparently works here. Looking deeper into what construct is used in the self-tests, that started working with that version would likely help, if someone is so inclined. Or, maybe it'd be ok to just disable the self-testing code before that version. Alternatively, plain raising the base version of the gcc being supported for gcc *development* to 4.7.4 would probably be acceptable too. To newcomers: remember, this is just the cross-gcc case.
