public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r13-6839] testsuite: Xfail gcc.dg/tree-ssa/ssa-fre-100.c for ! natural_alignment_32
Date: Thu, 23 Mar 2023 20:53:31 +0000 (GMT)	[thread overview]
Message-ID: <20230323205331.05E673858C50@sourceware.org> (raw)

https://gcc.gnu.org/g:3fbeff66684d95417646aaa22d0a8f1ec9786299

commit r13-6839-g3fbeff66684d95417646aaa22d0a8f1ec9786299
Author: Hans-Peter Nilsson <hp@axis.com>
Date:   Thu Mar 23 15:46:05 2023 +0100

    testsuite: Xfail gcc.dg/tree-ssa/ssa-fre-100.c for ! natural_alignment_32
    
    The test gcc.dg/tree-ssa/ssa-fre-100.c fails the
    scan-tree-dump-not fre1 "baz" for at least m68k-linux,
    pru-elf, and cris-elf according to posts on gcc-testresults.
    
    GCC requires int-size-alignment for a target to see through
    the "int *" dereference and perform value-numbering.  See
    comments in PR91419 and also the recent patch to
    gcc.dg/tree-ssa/pr100359.c.  This is a flaw in gcc rather
    than the target, so prefer an xfail rather than skipping
    the test.
    
            * gcc.dg/tree-ssa/ssa-fre-100.c: XFAIL for ! natural_alignment_32.

Diff:
---
 gcc/testsuite/gcc.dg/tree-ssa/ssa-fre-100.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/gcc.dg/tree-ssa/ssa-fre-100.c b/gcc/testsuite/gcc.dg/tree-ssa/ssa-fre-100.c
index ead76548f3d..1b6a3a398a4 100644
--- a/gcc/testsuite/gcc.dg/tree-ssa/ssa-fre-100.c
+++ b/gcc/testsuite/gcc.dg/tree-ssa/ssa-fre-100.c
@@ -22,4 +22,4 @@ void foo (int *p, int n)
   while (--n);
 }
 
-/* { dg-final { scan-tree-dump-not "baz" "fre1" } } */
+/* { dg-final { scan-tree-dump-not "baz" "fre1" { xfail { ! natural_alignment_32 } } } } */

                 reply	other threads:[~2023-03-23 20:53 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=20230323205331.05E673858C50@sourceware.org \
    --to=hp@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).