public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alex Coplan <acoplan@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-4741] aarch64, testsuite: Tweak sve/pcs/args_9.c to allow stps
Date: Thu, 19 Oct 2023 10:15:09 +0000 (GMT)	[thread overview]
Message-ID: <20231019101509.EBFEB38582B0@sourceware.org> (raw)

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

commit r14-4741-gcf776eebe86b8b75697de55a6a8ade72ce9f66c5
Author: Alex Coplan <alex.coplan@arm.com>
Date:   Wed Oct 4 14:13:00 2023 +0100

    aarch64, testsuite: Tweak sve/pcs/args_9.c to allow stps
    
    With the new ldp/stp pass enabled, there is a change in the codegen for
    this test as follows:
    
            add     x8, sp, 16
            ptrue   p3.h, mul3
            str     p3, [x8]
    -       str     x8, [sp, 8]
    -       str     x9, [sp]
    +       stp     x9, x8, [sp]
            ptrue   p3.d, vl8
            ptrue   p2.s, vl7
            ptrue   p1.h, vl6
    
    i.e. we now form an stp that we were missing previously. This patch
    adjusts the scan-assembler such that it should pass whether or not
    we form the stp.
    
    gcc/testsuite/ChangeLog:
    
            * gcc.target/aarch64/sve/pcs/args_9.c: Adjust scan-assemblers to
            allow for stp.

Diff:
---
 gcc/testsuite/gcc.target/aarch64/sve/pcs/args_9.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/testsuite/gcc.target/aarch64/sve/pcs/args_9.c b/gcc/testsuite/gcc.target/aarch64/sve/pcs/args_9.c
index ad9affadf02a..942a44ab4483 100644
--- a/gcc/testsuite/gcc.target/aarch64/sve/pcs/args_9.c
+++ b/gcc/testsuite/gcc.target/aarch64/sve/pcs/args_9.c
@@ -45,5 +45,5 @@ caller (int64_t *x0, int16_t *x1, svbool_t p0)
   return svcntp_b8 (res, res);
 }
 
-/* { dg-final { scan-assembler {\tptrue\t(p[0-9]+)\.b, mul3\n\tstr\t\1, \[(x[0-9]+)\]\n.*\tstr\t\2, \[sp\]\n} } } */
-/* { dg-final { scan-assembler {\tptrue\t(p[0-9]+)\.h, mul3\n\tstr\t\1, \[(x[0-9]+)\]\n.*\tstr\t\2, \[sp, 8\]\n} } } */
+/* { dg-final { scan-assembler {\tptrue\t(p[0-9]+)\.b, mul3\n\tstr\t\1, \[(x[0-9]+)\]\n.*\t(?:str\t\2, \[sp\]|stp\t\2, x[0-9]+, \[sp\])\n} } } */
+/* { dg-final { scan-assembler {\tptrue\t(p[0-9]+)\.h, mul3\n\tstr\t\1, \[(x[0-9]+)\]\n.*\t(?:str\t\2, \[sp, 8\]|stp\tx[0-9]+, \2, \[sp\])\n} } } */

                 reply	other threads:[~2023-10-19 10:15 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=20231019101509.EBFEB38582B0@sourceware.org \
    --to=acoplan@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).