public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Martin Sebor <msebor@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-2600] Xfail just the failing assertion and correct target.
Date: Thu, 29 Jul 2021 16:13:59 +0000 (GMT)	[thread overview]
Message-ID: <20210729161359.B6A9F385E44A@sourceware.org> (raw)

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

commit r12-2600-g2f6bdd51cfe15403085b69c133065ebda4af9bb9
Author: Martin Sebor <msebor@redhat.com>
Date:   Thu Jul 29 10:11:18 2021 -0600

    Xfail just the failing assertion and correct target.
    
    Related to:
    PR middle-end/101674 - gcc.dg/uninit-pred-9_b.c fails after jump threading rewrite
    
    gcc/testsuite:
            PR middle-end/101674
            * gcc.dg/uninit-pred-9_b.c: Xfail just the failing assertion and
            correct target.

Diff:
---
 gcc/testsuite/gcc.dg/uninit-pred-9_b.c | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/gcc/testsuite/gcc.dg/uninit-pred-9_b.c b/gcc/testsuite/gcc.dg/uninit-pred-9_b.c
index d46d6659a61..e0dc21405f7 100644
--- a/gcc/testsuite/gcc.dg/uninit-pred-9_b.c
+++ b/gcc/testsuite/gcc.dg/uninit-pred-9_b.c
@@ -1,7 +1,5 @@
-
 /* { dg-do compile } */
 /* { dg-options "-Wuninitialized -O2" } */
-/* { dg-xfail-if "threading shuffles things around" { ppc64*-*-* } } */
 
 int g;
 void bar();
@@ -22,7 +20,7 @@ int foo (int n, int l, int m, int r)
       blah(v); /* { dg-bogus "uninitialized" "bogus warning" } */
 
   if ( (n <= 8) &&  (m < 99)  && (r < 19) )
-      blah(v); /* { dg-bogus "uninitialized" "bogus warning" } */
+      blah(v); /* { dg-bogus "uninitialized" "pr101674" { xfail powerpc64*-*-* } } */
 
   return 0;
 }


                 reply	other threads:[~2021-07-29 16:13 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=20210729161359.B6A9F385E44A@sourceware.org \
    --to=msebor@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).