public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r14-9010] arm: testuite: Missing optimization pattern for rev16 with thumb1
Date: Thu, 15 Feb 2024 14:34:45 +0000 (GMT)	[thread overview]
Message-ID: <20240215143445.C2A2B3864C65@sourceware.org> (raw)

https://gcc.gnu.org/g:2acf478bf10fc38e9cbce77ac5ecaf5abfb724b1

commit r14-9010-g2acf478bf10fc38e9cbce77ac5ecaf5abfb724b1
Author: Matthieu Longo <matthieu.longo@arm.com>
Date:   Thu Feb 8 18:13:49 2024 +0000

    arm: testuite: Missing optimization pattern for rev16 with thumb1
    
    This patch marks a rev16 test as XFAIL for architectures having only
    Thumb1 support.  The generated code is functionally correct, but the
    optimization is disabled when -mthumb is equivalent to Thumb1.  Fixing
    the root issue would requires changes that are not suitable for GCC14
    stage 4.  More information at
    https://linaro.atlassian.net/browse/GNU-1141
    
    gcc/testsuite/ChangeLog:
    
            * gcc.target/arm/rev16_2.c: XFAIL when compiled with Thumb1.

Diff:
---
 gcc/testsuite/gcc.target/arm/rev16_2.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.target/arm/rev16_2.c b/gcc/testsuite/gcc.target/arm/rev16_2.c
index c6553b38a000..dff66e10bb93 100644
--- a/gcc/testsuite/gcc.target/arm/rev16_2.c
+++ b/gcc/testsuite/gcc.target/arm/rev16_2.c
@@ -17,4 +17,4 @@ __rev16_32 (__u32 x)
          | (((__u32)(x) & (__u32)0xff00ff00UL) >> 8);
 }
 
-/* { dg-final { scan-assembler-times {rev16\tr[0-9]+, r[0-9]+} 2 } } */
+/* { dg-final { scan-assembler-times {rev16\tr[0-9]+, r[0-9]+} 2 { xfail arm_thumb1_ok } } } */
\ No newline at end of file

                 reply	other threads:[~2024-02-15 14:34 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=20240215143445.C2A2B3864C65@sourceware.org \
    --to=rearnsha@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).