https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106472
--- Comment #30 from Eric Gallager <egallager at gcc dot gnu.org> --- (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
