public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-6068] Change the xfail in gcc.dg/uninit-pr89230-1.c
Date: Sun, 19 Dec 2021 22:36:37 +0000 (GMT)	[thread overview]
Message-ID: <20211219223637.5AD023858412@sourceware.org> (raw)

https://gcc.gnu.org/g:78fe0f23c73bf3b5d49dd2992d445bcc5db5a55c

commit r12-6068-g78fe0f23c73bf3b5d49dd2992d445bcc5db5a55c
Author: Andrew Pinski <apinski@marvell.com>
Date:   Sun Dec 19 22:26:41 2021 +0000

    Change the xfail in gcc.dg/uninit-pr89230-1.c
    
    With the recent PHI-OPT patch for line numbers, I had missed this
    testcase was now failing. The uninitialized warning was there
    before my recent patch, just was on the wrong line. The testcase
    had added an xfail in r12-4698-gf6d012338 (though a bug report was
    not filed to record it).
    This patch changes the dg-bogus messages around to catch both locations
    and xfail both of them.
    
    At least there is now a patch for the correct line numbers for the
    phi-opt.
    
    Committed after testing the testcase.
    
    gcc/testsuite/ChangeLog:
    
            * gcc.dg/uninit-pr89230-1.c: Change the dg-bogus messages
            around and xfail both of them.

Diff:
---
 gcc/testsuite/gcc.dg/uninit-pr89230-1.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/gcc/testsuite/gcc.dg/uninit-pr89230-1.c b/gcc/testsuite/gcc.dg/uninit-pr89230-1.c
index dfc87a5b1a0..bf536e2e65a 100644
--- a/gcc/testsuite/gcc.dg/uninit-pr89230-1.c
+++ b/gcc/testsuite/gcc.dg/uninit-pr89230-1.c
@@ -9,7 +9,7 @@ struct S { int i, j; };
 int g (void)
 {
   struct S *p = f ();
-  struct S *q; // { dg-bogus "may be used uninitialized" "uninitialized" { xfail *-*-* } }
+  struct S *q; // { dg-bogus "" "uninitialized" { xfail *-*-* } }
 
   if (p->i || !(q = f ()) || p->j != q->i)
    {
@@ -18,7 +18,7 @@ int g (void)
      if (p->i)
        return 1;
 
-     if (!q)        // { dg-bogus "\\\[-Wmaybe-uninitialized" }
+     if (!q)        // { dg-bogus "\\\[-Wmaybe-uninitialized" "" { xfail *-*-* } }
        return 2;
    }


                 reply	other threads:[~2021-12-19 22:36 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=20211219223637.5AD023858412@sourceware.org \
    --to=pinskia@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).