This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug bootstrap/52509] target libstdc++-v3 should not be bootstrapped, libstdc++-v3 should also be a host_module (bootstrapped)
- From: "egallager at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 22 Jul 2017 17:19:15 +0000
- Subject: [Bug bootstrap/52509] target libstdc++-v3 should not be bootstrapped, libstdc++-v3 should also be a host_module (bootstrapped)
- Auto-submitted: auto-generated
- References: <bug-52509-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=52509
Eric Gallager <egallager at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2017-07-22
CC| |egallager at gcc dot gnu.org
Ever confirmed|0 |1
--- Comment #4 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #2)
> (In reply to comment #1)
> > Well, for profiledbootstrap I think it is nice if target-libstdc++-v3 is
> > actually bootstrapped, because then we are able to train the C++ FE on real C++
> > code.
>
> Well, we bootstrap the host-libstdc++, that should be enough, no?
>
> Bootstrapping libstdc++ multilib and with building the PCHs is excessive
> waste of resources for building GCC with a C++ compiler.
Confirming that bootstrapping libstdc++ with multilibs is an excessive waste of
resources.