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/95969] Use of __builtin_aarch64_im_lane_boundsi in AArch64 arm_neon.h interferes with gimple optimisation
Date: Mon, 13 Sep 2021 15:19:39 +0000	[thread overview]
Message-ID: <bug-95969-4-sFKzmWoXaE@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95969-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from CVS 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:03312cbd54f337dfb25be356a1d1abc9925c6c03

commit r12-3493-g03312cbd54f337dfb25be356a1d1abc9925c6c03
Author: Andrew Pinski <apinski@marvell.com>
Date:   Thu Sep 2 07:08:22 2021 +0000

    [aarch64] Fix target/95969: __builtin_aarch64_im_lane_boundsi interferes
with gimple

    This patch adds simple folding of __builtin_aarch64_im_lane_boundsi where
    we are not going to error out. It fixes the problem by the removal
    of the function from the IR.

    OK? Bootstrapped and tested on aarch64-linux-gnu with no regressions.

    gcc/ChangeLog:

            PR target/95969
            * config/aarch64/aarch64-builtins.c
(aarch64_fold_builtin_lane_check):
            New function.
            (aarch64_general_fold_builtin): Handle
AARCH64_SIMD_BUILTIN_LANE_CHECK.
            (aarch64_general_gimple_fold_builtin): Likewise.

    gcc/testsuite/ChangeLog:

            PR target/95969
            * gcc.target/aarch64/lane-bound-1.c: New test.
            * gcc.target/aarch64/lane-bound-2.c: New test.

  parent reply	other threads:[~2021-09-13 15:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-29 15:50 [Bug target/95969] New: " rsandifo at gcc dot gnu.org
2021-09-02  5:31 ` [Bug target/95969] " pinskia at gcc dot gnu.org
2021-09-02  5:32 ` pinskia at gcc dot gnu.org
2021-09-02  7:14 ` pinskia at gcc dot gnu.org
2021-09-02  8:28 ` ktkachov at gcc dot gnu.org
2021-09-02  8:37 ` pinskia at gcc dot gnu.org
2021-09-02 10:35 ` pinskia at gcc dot gnu.org
2021-09-02 20:51 ` pinskia at gcc dot gnu.org
2021-09-02 22:26 ` pinskia at gcc dot gnu.org
2021-09-13 15:19 ` cvs-commit at gcc dot gnu.org [this message]
2021-09-13 15:20 ` 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-95969-4-sFKzmWoXaE@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).