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: dje at watson dot ibm dot com (David Edelsohn)
- Cc: rth at redhat dot com, mark at codesourcery dot com, gcc-patches at gcc dot gnu dot org
- Date: Wed, 13 Feb 2002 15:36:01 -0500 (EST)
- Subject: Re: Always link against static libgcc on hppa-linux
> If the December patch introduced some PA failures, I am sorry.
> Presumably things worked until the December patch was installed. Did you
> report a problem with the earlier patch? No. Simply reverting the
> December patch without even calling it a reversion is unacceptable. This
> is not a game of the last patch wins.
I wasn't aware of your earlier patch.
> Loading extra platform-specific stuff into libgcc.a is what is
> causing the problem. Why don't you place the millicode into another
> object file added to the GCC link line for your platform? libgcc.a now
> has a well-defined API. The PA millicode routines are not part of that
> API.
The decision to put the milli routines in libgcc was made years ago
for non HP systems. This was never an issue until we had a shared
libgcc. The advantage of putting the routines in libgcc is that
it consolidates the necessary low-level routines in one library and
the infrastructure to do that exists and is simple to use. If we
abandonned this approach, we would have to provide custom Makefile
modifications to build and install the milli.a library.
Dave
--
J. David Anglin dave.anglin@nrc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6605)