This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Graphite merge regressed PR 35107 ?
- From: "Kaveh R. GHAZI" <ghazi at caip dot rutgers dot edu>
- To: gcc at gcc dot gnu dot org
- Cc: gcc-bugs at gcc dot gnu dot org
- Date: Wed, 19 Nov 2008 16:49:48 -0500 (EST)
- Subject: Graphite merge regressed PR 35107 ?
PR 35107 appears to have regressed on mainline. It was originally fixed
on the trunk and 4.3 back in February:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35107
http://gcc.gnu.org/ml/gcc-patches/2008-02/msg00187.html
The summary is that gmp and mpfr and unnecessarily linked into all
executables (e.g. xgcc, gcov) whereas they should only be used for
programs that are linked with libbackend.a like cc1. It matters when
gmp/mpfr are shared libs. There's no reason to slow down the startup of
all programs we provide by dynamically loading these libraries.
During the graphite merge, $GMPLIBS was added back to the generic $LIBS
variable and gets linked into everything. Is this really necessary?
http://gcc.gnu.org/viewcvs/trunk/gcc/Makefile.in?r1=139854&r2=139893
If it's not necessary, IMHO this should be fixed again before we branch
4.4. I think CLOOGLIBS and PPLLIBS need to be moved to the right places,
but I don't have those libraries to test it myself. Since it would touch
all the places my original patch did, perhaps it would be best to create a
BACKENDLIBS and/or BACKENDDEPS variable and hook GMPLIBS, CLOOGLIBS and
PPLLIBS in there.
Thanks,
--Kaveh
--
Kaveh R. Ghazi ghazi@caip.rutgers.edu