From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Cc: nd@arm.com
Subject: Re: [PATCH][AArch64] Use builtins for fpcr/fpsr
Date: Fri, 09 Feb 2018 17:34:00 -0000 [thread overview]
Message-ID: <4e242f56-2c42-ee67-a6f2-78825ea76173@arm.com> (raw)
In-Reply-To: <DB6PR0801MB20535E76ABF67E12E616C0F083F20@DB6PR0801MB2053.eurprd08.prod.outlook.com>
On 09/02/18 15:03, Wilco Dijkstra wrote:
> Since GCC has support for accessing FPSR/FPCR, use them when possible
> so that the asm instructions can be removed eventually. Although GCC 5
> supports the builtins, it has an optimization bug, so use them from GCC 6
> onwards.
>
> GLIBC build and test OK.
>
> ChangeLog:
> 2018-01-19 Wilco Dijkstra <wdijkstr@arm.com>
>
> Â Â Â Â Â Â Â * sysdeps/aarch64/fpu/fpu_control.h: Use builtins for accessing FPCR/FPSR.
>
ok to commit.
next prev parent reply other threads:[~2018-02-09 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 11:38 Wilco Dijkstra
2018-01-18 13:57 ` Szabolcs Nagy
2018-01-19 13:18 ` Wilco Dijkstra
2018-02-09 15:06 ` Wilco Dijkstra
2018-02-09 17:34 ` Szabolcs Nagy [this message]
2018-02-09 23:23 ` Joseph Myers
2018-02-10 18:16 ` Wilco Dijkstra
2018-02-12 14:13 ` Joseph 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=4e242f56-2c42-ee67-a6f2-78825ea76173@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=Wilco.Dijkstra@arm.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).