From: James Greenhalgh <james.greenhalgh@arm.com>
To: Joel Hutton <Joel.Hutton@arm.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Richard Sandiford <Richard.Sandiford@arm.com>,
Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
Richard Earnshaw <Richard.Earnshaw@arm.com>, nd <nd@arm.com>
Subject: Re: [PING][AArch64] Use scvtf fbits option where appropriate
Date: Mon, 01 Jul 2019 17:03:00 -0000 [thread overview]
Message-ID: <20190701170311.GC23283@arm.com> (raw)
In-Reply-To: <832dd1bd-89f9-ca98-7b88-d5b26f515d63@arm.com>
On Wed, Jun 26, 2019 at 10:35:00AM +0100, Joel Hutton wrote:
> Ping, plus minor rework (mostly non-functional changes)
>
> gcc/ChangeLog:
>
> 2019-06-12 Joel Hutton <Joel.Hutton@arm.com>
>
> * config/aarch64/aarch64-protos.h (aarch64_fpconst_pow2_recip): New prototype
> * config/aarch64/aarch64.c (aarch64_fpconst_pow2_recip): New function
> * config/aarch64/aarch64.md (*aarch64_<su_optab>cvtf<fcvt_target><GPF:mode>2_mult): New pattern
Cool; I learned a new instruction!
> (*aarch64_<su_optab>cvtf<fcvt_iesize><GPF:mode>2_mult): New pattern
> * config/aarch64/constraints.md (Dt): New constraint
> * config/aarch64/predicates.md (aarch64_fpconst_pow2_recip): New predicate
>
> gcc/testsuite/ChangeLog:
>
> 2019-06-12 Joel Hutton <Joel.Hutton@arm.com>
>
> * gcc.target/aarch64/fmul_scvtf_1.c: New test.
This testcase will fail on ILP32 targets where unsigned long will still
live in a 'w' register.
Thanks,
James
next prev parent reply other threads:[~2019-07-01 17:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 17:26 [AArch64] " Wilco Dijkstra
2019-06-18 9:11 ` Joel Hutton
2019-06-18 10:37 ` Richard Earnshaw (lists)
2019-06-18 11:12 ` Wilco Dijkstra
2019-06-18 12:30 ` Richard Sandiford
2019-06-18 15:34 ` Joel Hutton
2019-06-26 9:35 ` [PING][AArch64] " Joel Hutton
2019-07-01 12:14 ` Wilco Dijkstra
2019-07-01 17:03 ` James Greenhalgh [this message]
2019-07-08 16:05 ` Joel Hutton
2019-08-19 17:47 ` James Greenhalgh
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=20190701170311.GC23283@arm.com \
--to=james.greenhalgh@arm.com \
--cc=Joel.Hutton@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=Richard.Sandiford@arm.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=gcc-patches@gcc.gnu.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).