https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106472
--- Comment #32 from Eric Gallager <egallager at gcc dot gnu.org> --- (In reply to matoro from comment #31) > (In reply to Eric Gallager from comment #30) > > (In reply to matoro from comment #26) > > > We also had somebody report on IRC that they observed this on powerpc (not > > > sure what tuple), again with -j1. It does not seem to show up with -j2, > > > so > > > likely -j1 is necessary to trigger. > > > > I can also confirm that switching to -j2 makes this particular error go away > > It may make it "go away", but how can it be worked around on real > single-core systems? All that does is get lucky by throwing more > parallelism at it. I've been completely unable to even try out gccgo > because of this bug. Right, yes, this is still definitely a bug, I was just confirming that I was able to get the workaround to work for me personally
