This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: egcs on AIX: native or gnu ld?
- To: David Edelsohn <dje at watson dot ibm dot com>
- Subject: Re: egcs on AIX: native or gnu ld?
- From: Andrey Slepuhin <pooh at msu dot ru>
- Date: Mon, 20 Oct 1997 13:41:27 +0400
- CC: egcs at cygnus dot com
- Organization: Moscow State University, Network Management Department
- References: <9710192145.AA33534@rios1.watson.ibm.com>
David Edelsohn wrote:
> These GLOBAL__DI/DD symbols exist for each library. collect2 and
> gnu ld collect all of the static constructors to be run at program startup
> -- both symbols within the program and symbols within any libraries. The
> GLOBAL__DI/DD symbols are present and duplicated in the executable because
> they are present in each library as a defining instance, but they never
> are referenced because collect2 has created a separate list of all of the
> constructor symbols for the executable.
Well, GLOBAL__DI/DD symbols are automatically exported by collect2. But
what
about __eh_<something> symbols, which are defined for each object file
and
are global bss symbols? Should I export them or they can be omitted?
I'm now looking into collect2 source to find appropriate place for
patching.
I see that collect2 exports some symbols by direct parsing of object
files.
As I don't know XCOFF file format I'll try to create separate export
list by calling a script. This is not a good solution so it should be
fixed
later. Well, when I obtain working version I'll send a patch.
Andrey.