From: Kito Cheng <kito.cheng@gmail.com>
To: Alexandre Oliva <oliva@adacore.com>
Cc: gcc-patches@gcc.gnu.org,
Rainer Orth <ro@cebitec.uni-bielefeld.de>,
Mike Stump <mikestump@comcast.net>
Subject: Re: [PATCH] [testsuite] [riscv] uninit-pred-9_b bogus warning
Date: Fri, 2 Dec 2022 17:37:29 +0800 [thread overview]
Message-ID: <CA+yXCZBL8xH9NBsqz3V6166oc+Rm-0xAgoTRZnS0GMou5rYj7Q@mail.gmail.com> (raw)
In-Reply-To: <or5yeuyxdv.fsf@lxoliva.fsfla.org>
OK, thanks :)
On Fri, Dec 2, 2022 at 5:21 PM Alexandre Oliva via Gcc-patches
<gcc-patches@gcc.gnu.org> wrote:
>
>
> Like other platforms, riscv hits the uninitialized warning because the
> optimizations don't eliminate the nonviable path that would enable it
> to be omitted.
>
> Regstraped on x86_64-linux-gnu, also tested with crosses to riscv64-elf
> and arm-eabi. Ok to install?
>
>
> for gcc/testsuite/ChangeLog
>
> * gcc.dg/uninit-pred-9_b.c: Add riscv*-*-* to the xfail list
> for the bogus warning.
> ---
> 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 53c4a5399eaa3..c8f427b12c0ab 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-*-* } } */
> --
> Alexandre Oliva, happy hacker https://FSFLA.org/blogs/lxo/
> Free Software Activist GNU Toolchain Engineer
> Disinformation flourishes because many people care deeply about injustice
> but very few check the facts. Ask me about <https://stallmansupport.org>
prev parent reply other threads:[~2022-12-02 9:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-02 9:21 Alexandre Oliva
2022-12-02 9:37 ` Kito Cheng [this message]
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=CA+yXCZBL8xH9NBsqz3V6166oc+Rm-0xAgoTRZnS0GMou5rYj7Q@mail.gmail.com \
--to=kito.cheng@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mikestump@comcast.net \
--cc=oliva@adacore.com \
--cc=ro@cebitec.uni-bielefeld.de \
/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).