This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: target/5842: [AIX] g++/collect2 extracts all static objects from archives
- From: dje at gcc dot gnu dot org
- To: dje at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, llattanz at flooz dot amer dot interwoven dot com, nobody at gcc dot gnu dot org
- Date: 13 Mar 2002 21:45:08 -0000
- Subject: Re: target/5842: [AIX] g++/collect2 extracts all static objects from archives
- Reply-to: dje at gcc dot gnu dot org, dje at gcc dot gnu dot org, gcc-bugs at gcc dot gnu dot org, gcc-prs at gcc dot gnu dot org, llattanz at flooz dot amer dot interwoven dot com, nobody at gcc dot gnu dot org, gcc-gnats at gcc dot gnu dot org
Synopsis: [AIX] g++/collect2 extracts all static objects from archives
Responsible-Changed-From-To: unassigned->dje
Responsible-Changed-By: dje
Responsible-Changed-When: Wed Mar 13 13:45:07 2002
Responsible-Changed-Why:
AIX
State-Changed-From-To: open->closed
State-Changed-By: dje
State-Changed-When: Wed Mar 13 13:45:07 2002
State-Changed-Why:
The report is not correct. collect2 does not add all objects
to the export list. collect2 does search all archives for
static contsructors and destructors and adds those to the
export list. Those constructors and destructors may pull
in more dependencies. Because the AIX linker garbage
collects symbols, if the symbol is not scanned and referenced
early (e.g., ctor/dtor), it may be omitted from the
executable.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5842