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: David Edelsohn <dje at watson dot ibm dot com>
- To: "John David Anglin" <dave at hiauly1 dot hia dot nrc dot ca>
- Cc: rth at redhat dot com, mark at codesourcery dot com, gcc-patches at gcc dot gnu dot org
- Date: Wed, 13 Feb 2002 16:16:48 -0500
- Subject: Re: Always link against static libgcc on hppa-linux
>>>>> John David Anglin writes:
John> The decision to put the milli routines in libgcc was made years ago
John> for non HP systems. This was never an issue until we had a shared
John> libgcc. The advantage of putting the routines in libgcc is that
John> it consolidates the necessary low-level routines in one library and
John> the infrastructure to do that exists and is simple to use. If we
John> abandonned this approach, we would have to provide custom Makefile
John> modifications to build and install the milli.a library.
The GCC configuration for AIX 3.2.5 explicitly added milli.exp to
its LINK_SPEC when those routines were not present in AIX libc. milli.exp
was copied to the install directory using EXTRA_PARTS. You do not need
custom Makefile modifications because the GCC Makefile already has the
necessary hooks.
Now that libgcc has a well-defined API and functions as a shared
library support library for GCC, it canont also be a platform support
library if the platform-specific additions interfere with its primary
purpose.
collect2 scans for EH frame info at the same time as constructors
and destructors. Teaching collect2 to ignore libgcc.a if it saw libgcc_s
is going to be very fragile.
David