public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/101325] [12 Regression] arm: Wrong code with MVE vcmpeqq intrinsic since r12-671-gd083fbf72
Date: Wed, 07 Jul 2021 11:39:01 +0000	[thread overview]
Message-ID: <bug-101325-4-Fdccd2YxTP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101325-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
(insn 7 4 8 2 (set (reg:HI 117)
        (eq:HI (reg:V16QI 119)
            (reg:V16QI 120))) {mve_vcmpeqq_v16qi}
     (expr_list:REG_DEAD (reg:V16QI 120)
        (expr_list:REG_DEAD (reg:V16QI 119)
            (nil))))

This is wrong.  EQ has a result of 0 or 1, regardless of the mode.

  parent reply	other threads:[~2021-07-07 11:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-05 15:57 [Bug target/101325] New: [12 Regression] arm: Wrong code with MVE vcmpeqq intrinsic acoplan at gcc dot gnu.org
2021-07-05 16:36 ` [Bug target/101325] " acoplan at gcc dot gnu.org
2021-07-06  6:29 ` rguenth at gcc dot gnu.org
2021-07-06  9:16 ` [Bug target/101325] [12 Regression] arm: Wrong code with MVE vcmpeqq intrinsic since r12-671-gd083fbf72 acoplan at gcc dot gnu.org
2021-07-06 10:13 ` clyon at gcc dot gnu.org
2021-07-07  8:19 ` clyon at gcc dot gnu.org
2021-07-07  8:29 ` clyon at gcc dot gnu.org
2021-07-07  8:37 ` clyon at gcc dot gnu.org
2021-07-07  9:54 ` clyon at gcc dot gnu.org
2021-07-07 11:25 ` clyon at gcc dot gnu.org
2021-07-07 11:39 ` rearnsha at gcc dot gnu.org [this message]
2021-07-07 12:13 ` clyon at gcc dot gnu.org
2021-07-07 12:42 ` rearnsha at gcc dot gnu.org
2021-07-09 15:31 ` clyon at gcc dot gnu.org
2022-01-17 14:05 ` rguenth at gcc dot gnu.org
2022-02-22 15:58 ` cvs-commit at gcc dot gnu.org
2022-02-22 15:58 ` cvs-commit at gcc dot gnu.org
2022-02-22 15:58 ` cvs-commit at gcc dot gnu.org
2022-02-22 15:58 ` cvs-commit at gcc dot gnu.org
2022-02-22 15:58 ` cvs-commit at gcc dot gnu.org
2022-02-22 15:58 ` cvs-commit at gcc dot gnu.org
2022-02-22 16:06 ` clyon at gcc dot gnu.org
2022-02-23  6:44 ` cvs-commit 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-101325-4-Fdccd2YxTP@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).