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: rth at redhat dot com (Richard Henderson)
- Cc: dje at watson dot ibm dot com, law at redhat dot com, mark at codesourcery dot com, gcc-patches at gcc dot gnu dot org
- Date: Thu, 14 Feb 2002 17:13:41 -0500 (EST)
- Subject: Re: Always link against static libgcc on hppa-linux
> On Fri, Feb 15, 2002 at 08:23:16AM +1030, Alan Modra wrote:
> > Yes, you can, but it's not the ideal place. The millicode routines
> > were put in libgcc.a (before the advent of a shared libgcc), as
> > they are arguably part of the compiler, as much as say, __divdi3.
>
> Well, libc contains the divide routines on alpha and the TFmode
> routines for sparc. This doesn't seem any different.
The main reason I don't like this is that, if we decide it would be
nice to have some other low-level function for the compiler, then we
have to go and negotiate to integrate it into a different package.
Dave
--
J. David Anglin dave.anglin@nrc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6605)