From: "Joseph S. Myers" <joseph@codesourcery.com>
To: Richard Henderson <rth@twiddle.net>
Cc: <libc-ports@sourceware.org>, <roland@hack.frob.com>
Subject: Re: [RFC] BZ 15666: alpha: Add __sqrt*_finite definitions
Date: Mon, 24 Jun 2013 20:24:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.64.1306242023040.31008@digraph.polyomino.org.uk> (raw)
In-Reply-To: <1372093627-26874-1-git-send-email-rth@twiddle.net>
On Mon, 24 Jun 2013, Richard Henderson wrote:
> Must I solve this with an explicit versioned_symbol macro, or is there
> a better way?
I don't have an answer to that question, but presume the complete patch
will also update sysdeps/unix/sysv/linux/alpha/nptl/libm.abilist to add
the new symbols to the expectations for the relevant symbol versions?
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2013-06-24 20:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-24 17:07 Richard Henderson
2013-06-24 20:24 ` Joseph S. Myers [this message]
2013-06-24 21:57 ` Roland McGrath
2013-06-25 0:10 ` Richard Henderson
2013-06-25 2:01 ` Richard Henderson
2013-06-25 13:35 ` Joseph S. Myers
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=Pine.LNX.4.64.1306242023040.31008@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=libc-ports@sourceware.org \
--cc=roland@hack.frob.com \
--cc=rth@twiddle.net \
/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).