public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Biener <rguenther@suse.de>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH] PR testsuite/111462 - add powerpc64le to list of ssa-sink-18.c XFAIL
Date: Mon, 30 Oct 2023 11:02:42 +0100 (CET)	[thread overview]
Message-ID: <20231030100243.17D80138F8@imap2.suse-dmz.suse.de> (raw)


Pushed.

	PR testsuite/111462
gcc/testsuite/
	* gcc.dg/tree-ssa/ssa-sink-18.c: XFAIL also powerpc64le.
---
 gcc/testsuite/gcc.dg/tree-ssa/ssa-sink-18.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/gcc/testsuite/gcc.dg/tree-ssa/ssa-sink-18.c b/gcc/testsuite/gcc.dg/tree-ssa/ssa-sink-18.c
index 13b9ba4f70f..1372100882e 100644
--- a/gcc/testsuite/gcc.dg/tree-ssa/ssa-sink-18.c
+++ b/gcc/testsuite/gcc.dg/tree-ssa/ssa-sink-18.c
@@ -1,5 +1,5 @@
 /* { dg-do compile } */
-/* { dg-options "-O2 -fdump-tree-sink-stats" } */
+/* { dg-options "-O2 -fdump-tree-sink2-stats" } */
 /* { dg-require-effective-target int32plus } */
 
 #include <stdint.h>
@@ -213,6 +213,6 @@ compute_on_bytes (uint8_t *in_data, int in_len, uint8_t *out_data, int out_len)
     expected, so this case is restricted to lp64 only so far.  This different
     ivopts choice affects riscv64 as well, probably because it also lacks
     base+index addressing modes, so the ip[len] address computation can't be
-    made from the IV computation above.  */
+    made from the IV computation above.  powerpc64le similarly is affected.  */
 
- /* { dg-final { scan-tree-dump-times "Sunk statements: 5" 1 "sink2" { target lp64 xfail { riscv64-*-* } } } } */
+ /* { dg-final { scan-tree-dump-times "Sunk statements: 5" 1 "sink2" { target lp64 xfail { riscv64-*-* powerpc64le-*-* } } } } */
-- 
2.35.3

                 reply	other threads:[~2023-10-30 10:02 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=20231030100243.17D80138F8@imap2.suse-dmz.suse.de \
    --to=rguenther@suse.de \
    --cc=gcc-patches@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).