public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/104396] New: [11/12 Regression] Invalid SIMD intriniscs accepted at -O1 and above after r11-6794-g04b472ad0e1dc93aba
Date: Sat, 05 Feb 2022 08:25:34 +0000	[thread overview]
Message-ID: <bug-104396-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 104396
           Summary: [11/12 Regression] Invalid SIMD intriniscs accepted at
                    -O1 and above after r11-6794-g04b472ad0e1dc93aba
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Keywords: accepts-invalid
          Severity: normal
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: pinskia at gcc dot gnu.org
  Target Milestone: ---
            Target: aarch64*-*-*

Take:

#include <arm_neon.h>

void f(int32x4_t *p0, int16x8_t *p1) {
    vqdmlal_high_laneq_s16(p0[0], p1[0], p1[1], -1);
}

This should be rejected even at -O1 but after r11-6794-g04b472ad0e1dc93aba, it
is accepted as the builtin is now removed with DCE.

See https://gcc.gnu.org/pipermail/gcc-patches/2022-February/589911.html also.

             reply	other threads:[~2022-02-05  8:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-05  8:25 pinskia at gcc dot gnu.org [this message]
2022-02-05  8:26 ` [Bug target/104396] " pinskia at gcc dot gnu.org
2022-02-07  7:49 ` rguenth at gcc dot gnu.org
2022-02-07 12:55 ` jakub at gcc dot gnu.org
2022-04-21  7:51 ` rguenth at gcc dot gnu.org
2023-05-29 10:06 ` [Bug target/104396] [11/12/13/14 " jakub 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-104396-4@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).