From: Zack Weinberg <zack@codesourcery.com>
To: Geoff Keating <geoffk@geoffk.org>
Cc: gcc@gcc.gnu.org
Subject: Re: Darwin assert.h / shared libgcc mess
Date: Mon, 22 Nov 2004 23:57:00 -0000 [thread overview]
Message-ID: <87oehp5xa8.fsf@codesourcery.com> (raw)
In-Reply-To: <97EC8AC0-3CD3-11D9-B3A6-000A95B1F520@geoffk.org> (Geoff Keating's message of "Mon, 22 Nov 2004 14:12:26 -0800")
Geoff Keating <geoffk@geoffk.org> writes:
> On 15/11/2004, at 3:39 PM, Zack Weinberg wrote:
>
>> Geoffrey Keating <geoffk@geoffk.org> writes:
>>
>>>> 2) Put __eprintf back into the shared libgcc, as an exported symbol,
>>>> for all !inhibit_libc targets, so that fixincludes can rely on its
>>>> being there. (If we instead use __assert, then __eprintf will
>>>> remain a static-library-only backward compatibility symbol.)
>>>
>>> Is this really necessary? I'd rather have __eprintf linked into only
>>> those apps that need it.
>>
>> Right now, any shared library that uses assert will fail to link.
>> _Something_ has to be done. I'm open to alternative suggestions.
>
> What I would do is put __eprintf in the static libgcc.a, and mark it as
> hidden visibility so that it's private to each shared library.
Indeed, right now I am pursuing just such an idea. It's not done
mainly because mklibgcc.in is very hard to modify.
zw
prev parent reply other threads:[~2004-11-22 22:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-15 21:43 Zack Weinberg
2004-11-15 22:42 ` Geoffrey Keating
2004-11-16 3:49 ` Zack Weinberg
2004-11-22 22:50 ` Geoff Keating
2004-11-22 23:57 ` Zack Weinberg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oehp5xa8.fsf@codesourcery.com \
--to=zack@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=geoffk@geoffk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).