public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/aoliva/heads/testme)] [testsuite] [riscv] uninit-pred-9_b bogus warning
Date: Thu,  1 Dec 2022 07:39:48 +0000 (GMT)	[thread overview]
Message-ID: <20221201073948.194B5385B185@sourceware.org> (raw)

https://gcc.gnu.org/g:fdf23207fe3a69bc35ac13633b9b3a7ccf95eb73

commit fdf23207fe3a69bc35ac13633b9b3a7ccf95eb73
Author: Alexandre Oliva <oliva@adacore.com>
Date:   Thu Dec 1 04:38:45 2022 -0300

    [testsuite] [riscv] uninit-pred-9_b bogus warning
    
    Like other platforms, riscv hits the uninitialized warning because the
    optimizations don't eliminate the nonviable path that would enable it
    to be omitted.
    
    
    for  gcc/testsuite/ChangeLog
    
            * gcc.dg/uninit-pred-9_b.c: Add riscv*-*-* to the xfail list
            for the bogus warning.
    
    Change-Id: I51e3848d6ac561a53ea8ea27c352b0b7b98a0d18
    TN: VB12-008

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

diff --git a/gcc/testsuite/gcc.dg/uninit-pred-9_b.c b/gcc/testsuite/gcc.dg/uninit-pred-9_b.c
index 53c4a5399ea..c8f427b12c0 100644
--- a/gcc/testsuite/gcc.dg/uninit-pred-9_b.c
+++ b/gcc/testsuite/gcc.dg/uninit-pred-9_b.c
@@ -17,7 +17,7 @@ int foo (int n, int l, int m, int r)
 
   if (l > 100)
     if ( (n <= 9) &&  (m < 100)  && (r < 19) )
-      blah(v); /* { dg-bogus "uninitialized" "bogus warning" { xfail powerpc64*-*-* cris-*-* } } */
+      blah(v); /* { dg-bogus "uninitialized" "bogus warning" { xfail powerpc64*-*-* cris-*-* riscv*-*-* } } */
 
   if ( (n <= 8) &&  (m < 99)  && (r < 19) )
       blah(v); /* { dg-bogus "uninitialized" "pr101674" { xfail mmix-*-* } } */

                 reply	other threads:[~2022-12-01  7:39 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=20221201073948.194B5385B185@sourceware.org \
    --to=aoliva@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).