https://gcc.gnu.org/bugzilla/show_bug.cgi?id=122613
--- Comment #3 from Sam James <sjames at gcc dot gnu.org> --- (In reply to Richard Biener from comment #2) > Hm, why do you not build a not-accelerator stage1 for building newlib then? That's what we do right now I think? A standalone tool outside of a package called crossdev (like crosstool-ng, etc) does the building of the stages + libc. We build stage2 with accelerator + openmp + fortran + whatever now that we have a libc (newlib). The stage2 is the only thing that we install. Then, on upgrades, we want to just use the stage2 to rebuild gcc to update itself, but we can't because it doesn't know how anymore. But we can't just rebuild the whole chain because it's not easy to express that in dependencies. The stage1 gets thrown away with our current design for things. I can try workaround it (e.g. do it all in-tree) but it would be a shame to only need to for one target.
