This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: New AIX libstdc++ testsuite regression 20_util/allocator_members
- From: David Edelsohn <dje at watson dot ibm dot com>
- To: Jason Merrill <jason at redhat dot com>
- Cc: bkoz at redhat dot com, Mark Mitchell <mark at codesourcery dot com>, libstdc++ at gcc dot gnu dot org
- Date: Tue, 23 Apr 2002 19:06:24 -0400
- Subject: Re: New AIX libstdc++ testsuite regression 20_util/allocator_members
>>>>> Jason Merrill writes:
>> The only thing I can think of if hacking up collect2 so that it
>> explicitly exports the mangled new and delete if it sees those symbol
>> names in the main application. But this just becomes an ever-increasing
>> list of useful mangled names to possibly export.
Jason> It would be simpler to just export everything, wouldn't it?
One also needs to invoke the "runtime linking" feature of the AIX
linker for the exported function to override the library. This is not the
default for G++.
My concern is how much to do things automatically versus how much
to allow the user to have control. Most people using GCC probably assume
SVR4-like semantics, but some people do develop code for the AIX model.
Automatically exporting all symbols and invoking runtime linking behavior
can cause problems in the opposite direction.
Unfortunately, there is no "right" answer.
David