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: mark at codesourcery dot com, rth at redhat dot com, gcc-patches at gcc dot gnu dot org
- Date: Thu, 14 Feb 2002 13:14:02 -0500
- Subject: Re: Always link against static libgcc on hppa-linux
>>>>> John David Anglin writes:
John> Can you point to any support routines that are in the static library
John> that aren't also in the shared library? I can't see how any of these
John> routines will ever be linked multiple times if proper linking procedures
John> are observed.
GCC EH relies on having only one copy of the EH routines in a
running executable: the main application, all shared libraries, and all
dynamically loaded shared objects. When we link against both shared and
static libraries, we run the risk of having multiple copies of the EH
routines. We especially do not want some parts of a running executable to
use tightly-bound versions of the routines distinct from other parts of
the executable.
In a single link-edit, I do not think that the linker could
reference the same symbol in multiple locations, but I am not an expert on
GNU ld. With shared libraries, shared objects, and pre-linking, I can
forsee potential problems.
David