https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106472
--- Comment #31 from matoro <matoro_gcc_bugzilla at matoro dot tk> --- (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.
