http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47368
Summary: CFLAGS_FOR_TARGET, profiledbootstrap and lto-bootstrap
flags unused in libstdc++-v3
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libstdc++
AssignedTo: unassig...@gcc.gnu.org
ReportedBy: howa...@nitro.med.uc.edu
When building with...
make -j profiledbootstrap BOOT_CFLAGS="-g -O3" CFLAGS_FOR_TARGET="-g -O3"
using the configure options...
Configured with: ../gcc-4.6-20110118/configure --prefix=/sw
--prefix=/sw/lib/gcc4.6 --mandir=/sw/share/man --infodir=/sw/lib/gcc4.6/info
--with-build-config=bootstrap-lto --enable-stage1-languages=c,lto
--enable-languages=c,c++,fortran,lto,objc,obj-c++,java --enable-build-with-cxx
--with-gmp=/sw --with-libiconv-prefix=/sw --with-ppl=/sw --with-cloog=/sw
--with-mpc=/sw --with-system-zlib --x-includes=/usr/X11R6/include
--x-libraries=/usr/X11R6/lib --program-suffix=-fsf-4.6 --enable-checking=yes
--enable-cloog-backend=isl
...libstdc++-v3 does not utilize the CFLAGS_FOR_TARGET="-g -O3" flags in its
build. This is unlike the other library directories such as libffi, libgcc,
libgfortran, libgomp, libiberty, libobjc, libquadmath and libssp which all
appear to use CFLAGS_FOR_TARGET.
The libstdc++-v3 build also doesn't utilize the profiling flags produced in
a profiledbootstrap or the lto flags produced from an lto-bootstrap.
