From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: "H.J. Lu" <hjl.tools@gmail.com>, Carlos O'Donell <carlos@redhat.com>
Cc: nd@arm.com, GNU C Library <libc-alpha@sourceware.org>
Subject: Re: [PATCH] x86-64: Use direct TLS initial-exec access to update errno
Date: Tue, 05 Dec 2017 10:24:00 -0000 [thread overview]
Message-ID: <5A2673C4.5050809@arm.com> (raw)
In-Reply-To: <CAMe9rOp1aBp6QoxTmYmBN5meNKoyMh6SVbLEyEsqc25uKY6gvQ@mail.gmail.com>
On 05/12/17 00:21, H.J. Lu wrote:
> On Mon, Dec 4, 2017 at 3:33 PM, Carlos O'Donell <carlos@redhat.com> wrote:
>> Why make these changes?
>
> It is motivated by
>
> https://sourceware.org/ml/libc-alpha/2017-12/msg00101.html
>
the failure paths of math functions are not
performance critical, ideally there should
be no errno access at all just a tail call
to something like __math_invalidf (see
flt-32/math_errf.c): reduces code size and
does all error handling at a single place
without tls abi dependent code in asm.
next prev parent reply other threads:[~2017-12-05 10:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 23:13 H.J. Lu
2017-12-04 23:33 ` Carlos O'Donell
2017-12-05 0:21 ` H.J. Lu
2017-12-05 10:24 ` Szabolcs Nagy [this message]
2017-12-05 13:47 ` Florian Weimer
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=5A2673C4.5050809@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=carlos@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.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).