From: Chris Metcalf <cmetcalf@tilera.com>
To: Andreas Schwab <schwab@suse.de>
Cc: Roland McGrath <roland@hack.frob.com>,
<libc-alpha@sourceware.org>, <libc-ports@sourceware.org>
Subject: Re: Fix SHLIB_COMPAT with undefined obsoleting version
Date: Mon, 11 Mar 2013 14:17:00 -0000 [thread overview]
Message-ID: <513DE784.2020504@tilera.com> (raw)
In-Reply-To: <mvmboaqqcrk.fsf@hawking.suse.de>
On 3/11/2013 9:36 AM, Andreas Schwab wrote:
> Chris Metcalf <cmetcalf@tilera.com> writes:
>
>> I'm a little confused by this. Why are you removing pthread_atfork from
>> the abilist files? It seems that calls to pthread_atfork() may have been
>> buggily redirected to pthread_atfork@GLIBC_2.12 for tilegx/tilepro,
> No, this is not possible.
>
>> but that doesn't mean we want to have NO implementation of
>> pthread_atfork exported from the library.
> The only implementation of pthread_atfork is in libpthread_nonshared.a.
Got it - we are actually calling libc.so's __register_atfork() due to the nonshared piece. What was confusing is that we appear to build pthread_atfork.os and then we don't use it.
--
Chris Metcalf, Tilera Corp.
http://www.tilera.com
next prev parent reply other threads:[~2013-03-11 14:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mvmr4juw5y8.fsf@hawking.suse.de>
[not found] ` <20130308215906.6B7A22C0A5@topped-with-meat.com>
2013-03-11 9:46 ` Andreas Schwab
2013-03-11 13:09 ` Chris Metcalf
2013-03-11 13:36 ` Andreas Schwab
2013-03-11 14:17 ` Chris Metcalf [this message]
2013-03-11 14:38 ` Andreas Schwab
2013-03-12 9:18 ` [PATCH] Don't build .os objects of static-only-routines for extra libs Andreas Schwab
2013-03-12 14:06 ` Carlos O'Donell
2013-03-12 15:40 ` Andreas Schwab
2013-03-12 22:24 ` Carlos O'Donell
2013-03-12 14:23 ` Chris Metcalf
2013-03-12 17:38 ` Roland McGrath
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=513DE784.2020504@tilera.com \
--to=cmetcalf@tilera.com \
--cc=libc-alpha@sourceware.org \
--cc=libc-ports@sourceware.org \
--cc=roland@hack.frob.com \
--cc=schwab@suse.de \
/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).