public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/71233] [ARM, AArch64] missing AdvSIMD intrinsics Date: Mon, 28 Sep 2020 13:01:10 +0000 [thread overview] Message-ID: <bug-71233-4-Sq54OyFiU1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-71233-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71233 --- Comment #53 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Kyrylo Tkachov <ktkachov@gcc.gnu.org>: https://gcc.gnu.org/g:677f34508f1c8fba6a52c77f83eca08b6762ed28 commit r10-8815-g677f34508f1c8fba6a52c77f83eca08b6762ed28 Author: Kyrylo Tkachov <kyrylo.tkachov@arm.com> Date: Wed Sep 23 17:37:58 2020 +0100 AArch64: Implement missing p128<->f64 reinterpret intrinsics This patch implements the missing reinterprets to and from poly128_t and float64x2_t. I've plugged in the appropriate testing in the advsimd-intrinsics.exp too. Bootstrapped and tested on aarch64-none-linux-gnu. Tested advsimd-intrinsics.exp on arm-none-eabi too to make sure arm testing isn't affected. gcc/ PR target/71233 * config/aarch64/arm_neon.h (vreinterpretq_f64_p128, vreinterpretq_p128_f64): Define. gcc/testsuite/ PR target/71233 * gcc.target/aarch64/advsimd-intrinsics/arm-neon-ref.h (clean_results): Add float64x2_t cleanup. (DECL_VARIABLE_128BITS_VARIANTS): Add float64x2_t variable. * gcc.target/aarch64/advsimd-intrinsics/vreinterpret_p128.c: Add testing of vreinterpretq_f64_p128, vreinterpretq_p128_f64. (cherry picked from commit 65c9878641cbe0ed898aa7047b7b994e9d4a5bb1)
next prev parent reply other threads:[~2020-09-28 13:01 UTC|newest] Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-71233-4@http.gcc.gnu.org/bugzilla/> 2020-09-01 12:39 ` clyon at gcc dot gnu.org 2020-09-01 12:39 ` clyon at gcc dot gnu.org 2020-09-01 13:42 ` clyon at gcc dot gnu.org 2020-09-01 13:42 ` clyon at gcc dot gnu.org 2020-09-01 13:42 ` clyon at gcc dot gnu.org 2020-09-01 13:47 ` clyon at gcc dot gnu.org 2020-09-01 14:08 ` clyon at gcc dot gnu.org 2020-09-01 14:09 ` clyon at gcc dot gnu.org 2020-09-01 14:09 ` clyon at gcc dot gnu.org 2020-09-01 14:43 ` clyon at gcc dot gnu.org 2020-09-01 14:43 ` clyon at gcc dot gnu.org 2020-09-10 8:59 ` sripar01 at gcc dot gnu.org 2020-09-22 11:06 ` cvs-commit at gcc dot gnu.org 2020-09-22 11:06 ` cvs-commit at gcc dot gnu.org 2020-09-22 11:06 ` cvs-commit at gcc dot gnu.org 2020-09-22 11:24 ` cvs-commit at gcc dot gnu.org 2020-09-23 9:35 ` cvs-commit at gcc dot gnu.org 2020-09-23 9:35 ` cvs-commit at gcc dot gnu.org 2020-09-23 10:08 ` cvs-commit at gcc dot gnu.org 2020-09-23 11:03 ` cvs-commit at gcc dot gnu.org 2020-09-23 16:39 ` cvs-commit at gcc dot gnu.org 2020-09-24 10:25 ` cvs-commit at gcc dot gnu.org 2020-09-24 10:25 ` cvs-commit at gcc dot gnu.org 2020-09-24 15:55 ` cvs-commit at gcc dot gnu.org 2020-09-24 15:57 ` cvs-commit at gcc dot gnu.org 2020-09-25 10:25 ` cvs-commit at gcc dot gnu.org 2020-09-25 10:32 ` cvs-commit at gcc dot gnu.org 2020-09-25 10:41 ` cvs-commit at gcc dot gnu.org 2020-09-25 16:09 ` cvs-commit at gcc dot gnu.org 2020-09-28 13:00 ` cvs-commit at gcc dot gnu.org 2020-09-28 13:00 ` cvs-commit at gcc dot gnu.org 2020-09-28 13:00 ` cvs-commit at gcc dot gnu.org 2020-09-28 13:00 ` cvs-commit at gcc dot gnu.org 2020-09-28 13:00 ` cvs-commit at gcc dot gnu.org 2020-09-28 13:00 ` cvs-commit at gcc dot gnu.org 2020-09-28 13:01 ` cvs-commit at gcc dot gnu.org 2020-09-28 13:01 ` cvs-commit at gcc dot gnu.org [this message] 2020-09-28 13:01 ` cvs-commit at gcc dot gnu.org 2020-09-28 15:19 ` cvs-commit at gcc dot gnu.org 2020-09-28 15:19 ` cvs-commit at gcc dot gnu.org 2020-09-28 15:19 ` cvs-commit at gcc dot gnu.org 2020-09-28 15:19 ` cvs-commit at gcc dot gnu.org 2020-09-28 15:19 ` cvs-commit at gcc dot gnu.org 2020-09-28 15:19 ` cvs-commit at gcc dot gnu.org 2020-09-28 15:19 ` cvs-commit at gcc dot gnu.org 2020-09-28 15:19 ` cvs-commit at gcc dot gnu.org 2020-09-28 15:19 ` cvs-commit at gcc dot gnu.org 2020-09-28 16:13 ` cvs-commit at gcc dot gnu.org 2020-09-28 16:14 ` cvs-commit at gcc dot gnu.org 2020-09-28 16:14 ` cvs-commit at gcc dot gnu.org 2020-09-28 16:14 ` cvs-commit at gcc dot gnu.org 2020-09-28 16:14 ` cvs-commit at gcc dot gnu.org 2020-09-28 16:14 ` cvs-commit at gcc dot gnu.org 2020-09-28 16:14 ` cvs-commit at gcc dot gnu.org 2020-09-28 16:14 ` cvs-commit at gcc dot gnu.org 2020-09-28 16:14 ` cvs-commit at gcc dot gnu.org 2021-01-12 14:58 ` clyon at gcc dot gnu.org 2021-01-15 12:39 ` cvs-commit at gcc dot gnu.org 2021-01-15 14:11 ` cvs-commit at gcc dot gnu.org 2021-05-04 12:31 ` rguenth at gcc dot gnu.org
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=bug-71233-4-Sq54OyFiU1@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).