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/107987] [12/13 Regression] MVE vcmpq vector-scalar can trigger ICE
Date: Tue, 06 Dec 2022 12:08:55 +0000	[thread overview]
Message-ID: <bug-107987-4-fKR72yZHPa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107987-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andre Simoes Dias Vieira
<avieira@gcc.gnu.org>:

https://gcc.gnu.org/g:ed34c3bc3428bce663d42e9eeda10bc0c5d56d5c

commit r13-4506-ged34c3bc3428bce663d42e9eeda10bc0c5d56d5c
Author: Andre Vieira <andre.simoesdiasvieira@arm.com>
Date:   Tue Dec 6 12:06:33 2022 +0000

    arm: Fix MVE's vcmp vector-scalar patterns [PR107987]

    This patch surrounds the scalar operand of the MVE vcmp patterns with a
    vec_duplicate to ensure both operands of the comparision operator have the
same
    (vector) mode.

    gcc/ChangeLog:

            PR target/107987
            * config/arm/mve.md (mve_vcmp<mve_cmp_op>q_n_<mode>,
            @mve_vcmp<mve_cmp_op>q_n_f<mode>): Apply vec_duplicate to scalar
            operand.

    gcc/testsuite/ChangeLog:

            * gcc.target/arm/mve/pr107987.c: New test.

  parent reply	other threads:[~2022-12-06 12:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06  9:42 [Bug target/107987] New: " avieira at gcc dot gnu.org
2022-12-06  9:54 ` [Bug target/107987] " rguenth at gcc dot gnu.org
2022-12-06 12:08 ` cvs-commit at gcc dot gnu.org [this message]
2023-01-27 12:16 ` [Bug target/107987] [12 " cvs-commit at gcc dot gnu.org
2023-01-27 14:07 ` avieira 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-107987-4-fKR72yZHPa@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).