From: Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Marcus Shawcroft <Marcus.Shawcroft@arm.com>,
James Greenhalgh <James.Greenhalgh@arm.com>,
Richard Earnshaw <Richard.Earnshaw@arm.com>
Subject: Re: [PATCH][AArch64] Implement ACLE intrinsics for FRINT[32,64][Z,X]
Date: Mon, 02 Sep 2019 12:41:00 -0000 [thread overview]
Message-ID: <2493a30d-fb4c-a43f-7bfc-09766867f844@foss.arm.com> (raw)
In-Reply-To: <1be1bead-8ea4-0ef2-2952-0b991e5d6621@foss.arm.com>
On 9/2/19 1:16 PM, Kyrill Tkachov wrote:
> Hi all,
>
> This patch implements the ACLE intrinsics to access the
> FRINT[32,64][Z,X] scalar[1] and vector[2][3] instructions
> from Armv8.5-a. These are enabled when the __ARM_FEATURE_FRINT macro is
> defined.
>
> They're added in a fairly standard way through builtins and unspecs at
> the RTL level.
> The scalar intrinsics
Sorry, some malfunction occurred.
The scalar intrinsics are available through <arm_acle.h> whereas the Adv
SIMD ones are in <arm_neon.h>
Thanks,
Kyrill
>
> Bootstrapped and tested on aarch64-none-linux-gnu.
>
> Ok for trunk?
> Thanks,
> Kyrill
>
> [1]
> https://developer.arm.com/docs/101028/latest/data-processing-intrinsics
> [2]
> https://developer.arm.com/architectures/instruction-sets/simd-isas/neon/intrinsics?page=2&search=vrnd32
> [3]
> https://developer.arm.com/architectures/instruction-sets/simd-isas/neon/intrinsics?page=2&search=vrnd64
>
> 2019-09-02 Kyrylo Tkachov <kyrylo.tkachov@arm.com>
>
> Â Â Â Â * config/aarch64/aarch64.md ("unspec"): Add UNSPEC_FRINT32Z,
> Â Â Â Â UNSPEC_FRINT32X, UNSPEC_FRINT64Z, UNSPEC_FRINT64X.
> Â Â Â Â (aarch64_<frintnzs_op><mode>): New define_insn.
> Â Â Â Â * config/aarch64/aarch64.h (TARGET_FRINT): Define.
> Â Â Â Â * config/aarch64/aarch64-c.c (aarch64_update_cpp_builtins): Define
> Â Â Â Â __ARM_FEATURE_FRINT when appropriate.
> Â Â Â Â * config/aarch64/aarch64-simd-builtins.def: Add builtins for
> frint32z,
> Â Â Â Â frint32x, frint64z, frint64x.
> Â Â Â Â * config/aarch64/arm_acle.h (__rint32zf, __rint32z, __rint64zf,
> Â Â Â Â __rint64z, __rint32xf, __rint32x, __rint64xf, __rint64x): Define.
> Â Â Â Â * config/aarch64/arm_neon.h (vrnd32z_f32, vrnd32zq_f32, vrnd32z_f64,
> Â Â Â Â vrnd32zq_f64, vrnd32x_f32, vrnd32xq_f32, vrnd32x_f64, vrnd32xq_f64,
> Â Â Â Â vrnd64z_f32, vrnd64zq_f32, vrnd64z_f64, vrnd64zq_f64, vrnd64x_f32,
> Â Â Â Â vrnd64xq_f32, vrnd64x_f64, vrnd64xq_f64): Define.
> Â Â Â Â * config/aarch64/iterators.md (VSFDF): Define.
> Â Â Â Â (FRINTNZX): Likewise.
> Â Â Â Â (frintnzs_op): Likewise.
>
> 2019-09-02 Kyrylo Tkachov <kyrylo.tkachov@arm.com>
>
> Â Â Â Â * gcc.target/aarch64/acle/rintnzx_1.c: New test.
> Â Â Â Â * gcc.target/aarch64/simd/vrndnzx_1.c: Likewise.
>
prev parent reply other threads:[~2019-09-02 12:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-02 12:16 Kyrill Tkachov
2019-09-02 12:41 ` Kyrill Tkachov [this message]
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=2493a30d-fb4c-a43f-7bfc-09766867f844@foss.arm.com \
--to=kyrylo.tkachov@foss.arm.com \
--cc=James.Greenhalgh@arm.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
/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).