[Bug bootstrap/52509] New: target libstdc++-v3 should not be bootstrapped, libstdc++-v3 should also be a host_module (bootstrapped)

[Bug bootstrap/52509] New: target libstdc++-v3 should not be bootstrapped, libstdc++-v3 should also be a host_module (bootstrapped)

[rguenth at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52509

             Bug #: 52509
           Summary: target libstdc++-v3 should not be bootstrapped,
                    libstdc++-v3 should also be a host_module
                    (bootstrapped)
    Classification: Unclassified
           Product: gcc
           Version: 4.7.0
            Status: UNCONFIRMED
          Keywords: build
          Severity: normal
          Priority: P3
         Component: bootstrap
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: rguenth@gcc.gnu.org


We should not need to bootstrap the target libstdc++ (and it's multilibs),
but we only need a host libstdc++ (of the host multilib variant - does
a canadian cross even work right now with C++ bootstrap?).  The host libstdc++
should be a static library only, and it should not build PCH files
(configured with --disable-libstdcxx-pch).

Thus, like simply

Index: Makefile.def
===================================================================
--- Makefile.def        (revision 184981)
+++ Makefile.def        (working copy)
@@ -84,6 +84,8 @@ host_modules= { module= libdecnumber; bo
 host_modules= { module= libgui; };
 host_modules= { module= libiberty; bootstrap=true;
               
extra_configure_flags='@extra_host_libiberty_configure_flags@';};
+host_modules= { module= libstdc++-v3; bootstrap=true;
+               extra_configure_flags='--disable-libstdcxx-pch';}
 // We abuse missing to avoid installing anything for libiconv.
 host_modules= { module= libiconv;
                extra_configure_flags='--disable-shared';
@@ -113,7 +115,6 @@ host_modules= { module= lto-plugin; boot
                extra_configure_flags=--enable-shared; };

 target_modules = { module= libstdc++-v3;
-                  bootstrap=true;
                   lib_path=src/.libs;
                   raw_cxx=true; };
 target_modules = { module= libmudflap; lib_path=.libs; };

?

[Bug bootstrap/52509] target libstdc++-v3 should not be bootstrapped, libstdc++-v3 should also be a host_module (bootstrapped)

[jakub at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52509

Jakub Jelinek <jakub at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jakub at gcc dot gnu.org

--- Comment #1 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-03-06 12:58:35 UTC ---
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.

[Bug bootstrap/52509] target libstdc++-v3 should not be bootstrapped, libstdc++-v3 should also be a host_module (bootstrapped)

[rguenth at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52509

--- Comment #2 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-03-06 13:15:37 UTC ---
(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.

[Bug bootstrap/52509] target libstdc++-v3 should not be bootstrapped, libstdc++-v3 should also be a host_module (bootstrapped)

[jakub at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52509

--- Comment #3 from Jakub Jelinek <jakub at gcc dot gnu.org> 2012-03-06 13:31:35 UTC ---
I guess bootstrapping of the host libstdc++-v3 if it is performed is fine.