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/102171] vget_low_*/vget_high_* intrinsics should become BIT_FIELD_REF during gimple
Date: Wed, 22 May 2024 20:07:50 +0000	[thread overview]
Message-ID: <bug-102171-4-2Hpx8zhkk1@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102171-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102171

--- Comment #5 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Andrew Pinski <pinskia@gcc.gnu.org>:

https://gcc.gnu.org/g:1d1ef1c22752b3e250ee769ae6d79f537471a57f

commit r15-778-g1d1ef1c22752b3e250ee769ae6d79f537471a57f
Author: Pengxuan Zheng <quic_pzheng@quicinc.com>
Date:   Tue May 21 10:55:06 2024 -0700

    aarch64: Fold vget_high_* intrinsics to BIT_FIELD_REF [PR102171]

    This patch is a follow-up of r15-697-ga2e4fe5a53cf75 to also fold
vget_high_*
    intrinsics to BIT_FILED_REF and remove the vget_high_* definitions from
    arm_neon.h to use the new intrinsics framework.

            PR target/102171

    gcc/ChangeLog:

            * config/aarch64/aarch64-builtins.cc
(AARCH64_SIMD_VGET_HIGH_BUILTINS):
            New macro to create definitions for all vget_high intrinsics.
            (VGET_HIGH_BUILTIN): Likewise.
            (enum aarch64_builtins): Add vget_high function codes.
            (AARCH64_SIMD_VGET_LOW_BUILTINS): Delete duplicate macro.
            (aarch64_general_fold_builtin): Fold vget_high calls.
            * config/aarch64/aarch64-simd-builtins.def: Delete vget_high
builtins.
            * config/aarch64/aarch64-simd.md (aarch64_get_high<mode>): Delete.
            (aarch64_vget_hi_halfv8bf): Likewise.
            * config/aarch64/arm_neon.h (__attribute__): Delete.
            (vget_high_f16): Likewise.
            (vget_high_f32): Likewise.
            (vget_high_f64): Likewise.
            (vget_high_p8): Likewise.
            (vget_high_p16): Likewise.
            (vget_high_p64): Likewise.
            (vget_high_s8): Likewise.
            (vget_high_s16): Likewise.
            (vget_high_s32): Likewise.
            (vget_high_s64): Likewise.
            (vget_high_u8): Likewise.
            (vget_high_u16): Likewise.
            (vget_high_u32): Likewise.
            (vget_high_u64): Likewise.
            (vget_high_bf16): Likewise.

    gcc/testsuite/ChangeLog:

            * gcc.target/aarch64/vget_high_2.c: New test.
            * gcc.target/aarch64/vget_high_2_be.c: New test.

    Signed-off-by: Pengxuan Zheng <quic_pzheng@quicinc.com>

  parent reply	other threads:[~2024-05-22 20:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-02  7:59 [Bug target/102171] New: " pinskia at gcc dot gnu.org
2021-10-22 10:10 ` [Bug target/102171] " tnfchris at gcc dot gnu.org
2024-02-27  9:28 ` pinskia at gcc dot gnu.org
2024-02-27  9:32 ` tnfchris at gcc dot gnu.org
2024-05-20 20:06 ` cvs-commit at gcc dot gnu.org
2024-05-22 20:07 ` cvs-commit at gcc dot gnu.org [this message]
2024-05-22 20:09 ` pinskia 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-102171-4-2Hpx8zhkk1@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: 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).