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-6367] testsuite: Remove xfail gcc.dg/tree-ssa/pr91091-2.c RHS ! natural_alignment_32
Date: Tue, 28 Feb 2023 01:23:30 +0000 (GMT)	[thread overview]
Message-ID: <20230228012330.ADAAC3858D32@sourceware.org> (raw)

https://gcc.gnu.org/g:5c70121c57c544a9afeb842984c9a0a36816c590

commit r13-6367-g5c70121c57c544a9afeb842984c9a0a36816c590
Author: Hans-Peter Nilsson <hp@axis.com>
Date:   Mon Feb 27 18:40:02 2023 +0100

    testsuite: Remove xfail gcc.dg/tree-ssa/pr91091-2.c RHS ! natural_alignment_32
    
    Reacting to a long-standing XPASS for CRIS.  This one is
    slightly brown paper-bag level; it was never the here-removed
    xfailed scan that failed and I didn't notice that XPASS when
    reporting success on the commit as a whole.  It's not logical to
    re-read what was just-written even with overlap issues, and I'm
    sure that edit was originally a copy-pasto.  I checked
    historical m68k-linux and pru-elf test-results too, to verify
    that I got that part right.
    
            PR testsuite/91419
            * gcc.dg/tree-ssa/pr91091-2.c:15 Remove xfail for RHS.

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

diff --git a/gcc/testsuite/gcc.dg/tree-ssa/pr91091-2.c b/gcc/testsuite/gcc.dg/tree-ssa/pr91091-2.c
index ecc50d355a7..79254150490 100644
--- a/gcc/testsuite/gcc.dg/tree-ssa/pr91091-2.c
+++ b/gcc/testsuite/gcc.dg/tree-ssa/pr91091-2.c
@@ -12,4 +12,4 @@ void swap(struct s* p, struct t* q)
 
 /* The second statement is redundant.  */
 /* { dg-final { scan-tree-dump-times "x = " 1 "fre1" { xfail { ! natural_alignment_32 } } } } */
-/* { dg-final { scan-tree-dump-times " = \[^;\]*x;" 1 "fre1" { xfail { ! natural_alignment_32 } } } } */
+/* { dg-final { scan-tree-dump-times " = \[^;\]*x;" 1 "fre1" } } */

                 reply	other threads:[~2023-02-28  1:23 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=20230228012330.ADAAC3858D32@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).