From: Roland McGrath <roland@hack.frob.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: libc-ports@sourceware.org, "Ryan S. Arnold" <ryan.arnold@gmail.com>
Subject: Re: powerpc-nofpu ABI baselines
Date: Wed, 16 May 2012 21:42:00 -0000 [thread overview]
Message-ID: <20120516214148.19DA22C0A8@topped-with-meat.com> (raw)
In-Reply-To: Joseph S. Myers's message of Wednesday, 16 May 2012 21:37:18 +0000 <Pine.LNX.4.64.1205162123360.32674@digraph.polyomino.org.uk>
> @@ -1845,6 +1844,31 @@
> __xpg_sigpause F
> __xstat64 F
> _flushlbf F
> + _q_add F
>
> [...]
>
> See <http://sourceware.org/ml/libc-ports/2007-10/msg00004.html>. These
> functions are in GLIBC_2.2 version but would not have been in glibc 2.2
> and would never actually have been useful. Do we want to record them as
> part of the GLIBC_2.2 ABI to preserve, or remove them?
The relevant question is when the bug came in such that _q_add was
exported. If it has been that way for some widely-used versions, then
it's likely that there are binaries referring to the symbol. In that
case, we can't really take it out even though it's an inaccurate
representation of what 2.2 was.
next prev parent reply other threads:[~2012-05-16 21:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-16 21:23 Joseph S. Myers
2012-05-16 21:37 ` Joseph S. Myers
2012-05-16 21:42 ` Roland McGrath [this message]
2012-05-16 21:58 ` Joseph S. Myers
2012-05-16 22:03 ` 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=20120516214148.19DA22C0A8@topped-with-meat.com \
--to=roland@hack.frob.com \
--cc=joseph@codesourcery.com \
--cc=libc-ports@sourceware.org \
--cc=ryan.arnold@gmail.com \
/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).