This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: weak for Darwin
- From: Jason Merrill <jason at redhat dot com>
- To: Matt Austern <austern at apple dot com>
- Cc: Benjamin Kosnik <bkoz at redhat dot com>, libstdc++ at gcc dot gnu dot org, gcc-patches at gcc dot gnu dot org, gkeating at apple dot com (Geoffrey Keating)
- Date: Mon, 01 Nov 2004 15:36:51 -0500
- Subject: Re: weak for Darwin
- References: <20041026060731.4F9AE1B4B330@geoffk5.apple.com><20041101125616.4827ec67.bkoz@redhat.com><4DA23D3C-2C3B-11D9-8AB5-000A95AA5E5E@apple.com>
On Mon, 1 Nov 2004 11:22:00 -0800, Matt Austern <austern@apple.com> wrote:
> On Nov 1, 2004, at 10:56 AM, Benjamin Kosnik wrote:
>
>>
>>> There is, however, a complication. The Darwin loader doesn't really
>>> handle weak symbols, or symbol overriding of any kind, unless you use
>>> flat namespaces. After the afore-mentioned discussion, we concluded
>>> that the best thing would be if the Darwin loader did handle this, and
>>> it's planned to be implemented (you'll note that the magic words
>>> "implemented now" did not appear in that sentence).
>>
>> Why hack up the FSF sources for this? Couldn't you just keep this on
>> your vendor branch?
>
> I don't see a good reason for that. Darwin is a supported OS, so the
> mainline compiler should be made to work well on Darwin.
Agreed.
Jason