public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Richard Sandiford <rsandifo@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-5346] aarch64: Restore generation of SVE UQDEC instructions
Date: Wed, 25 Jan 2023 11:24:54 +0000 (GMT)	[thread overview]
Message-ID: <20230125112454.72B393858C31@sourceware.org> (raw)

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

commit r13-5346-gda43e287d1917a25594f95c7c519ded637c7ea50
Author: Richard Sandiford <richard.sandiford@arm.com>
Date:   Wed Jan 25 11:24:32 2023 +0000

    aarch64: Restore generation of SVE UQDEC instructions
    
    The addition of TARGET_CSSC meant that we wouldn't generate SVE
    UQDEC instructions unless +cssc was also enabled.
    
    Fixes:
    - gcc.target/aarch64/sve/slp_4.c
    - gcc.target/aarch64/sve/slp_10.c
    - gcc.target/aarch64/sve/while_4.c
    
    gcc/
            * config/aarch64/aarch64.md (umax<mode>3): Separate the CNT and CSSC
            tests.

Diff:
---
 gcc/config/aarch64/aarch64.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/gcc/config/aarch64/aarch64.md b/gcc/config/aarch64/aarch64.md
index e4d7587aac7..0b326d497b4 100644
--- a/gcc/config/aarch64/aarch64.md
+++ b/gcc/config/aarch64/aarch64.md
@@ -4457,8 +4457,9 @@
   {
     if (aarch64_sve_cnt_immediate (operands[1], <MODE>mode))
       std::swap (operands[1], operands[2]);
-    else if (!aarch64_sve_cnt_immediate (operands[2], <MODE>mode)
-	     && TARGET_CSSC)
+    else if (aarch64_sve_cnt_immediate (operands[2], <MODE>mode))
+      ;
+    else if (TARGET_CSSC)
       {
 	if (aarch64_uminmax_immediate (operands[1], <MODE>mode))
 	  std::swap (operands[1], operands[2]);

                 reply	other threads:[~2023-01-25 11:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230125112454.72B393858C31@sourceware.org \
    --to=rsandifo@gcc.gnu.org \
    --cc=gcc-cvs@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).