This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: Always link against static libgcc on hppa-linux
- From: "John David Anglin" <dave at hiauly1 dot hia dot nrc dot ca>
- To: mark at codesourcery dot com (Mark Mitchell)
- Cc: dje at watson dot ibm dot com, rth at redhat dot com, gcc-patches at gcc dot gnu dot org
- Date: Thu, 14 Feb 2002 16:31:04 -0500 (EST)
- Subject: Re: Always link against static libgcc on hppa-linux
> We still need to figure out what to do for 3.1.
I would would suggest that gcc.c be changed to only link the shared
library. I will temporarily hack the pa/pa-linux.h file to work
around the problem until we find what to do with the milli routines.
> The issues with linking libgcc twice are only partly about code; even
> more important is data. There is global data in libgcc that must be
> present exactly once in the final executable.
There isn't any under hppa-linux. Under hppa64-hp-hpux, we have
__[CD]TOR_LIST__ referenced by __main. We would know quickly if
that was broken.
Dave
--
J. David Anglin dave.anglin@nrc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6605)