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 r11-8179] PR testsuite/100073 - test case gcc.dg/pr86058.c fails on arm, powerpc64 Date: Wed, 14 Apr 2021 16:45:44 +0000 (GMT) [thread overview] Message-ID: <20210414164544.4EAF13851C2B@sourceware.org> (raw) https://gcc.gnu.org/g:785209fc464ee3efec2b2a8e8244b7292c251ad8 commit r11-8179-g785209fc464ee3efec2b2a8e8244b7292c251ad8 Author: Martin Sebor <msebor@redhat.com> Date: Wed Apr 14 10:43:22 2021 -0600 PR testsuite/100073 - test case gcc.dg/pr86058.c fails on arm, powerpc64 gcc/testsuite/ChangeLog: * gcc.dg/pr86058.c: Limit to just x86_64. Diff: --- gcc/testsuite/gcc.dg/pr86058.c | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/gcc/testsuite/gcc.dg/pr86058.c b/gcc/testsuite/gcc.dg/pr86058.c index 0b030b04acf..e39b7207b82 100644 --- a/gcc/testsuite/gcc.dg/pr86058.c +++ b/gcc/testsuite/gcc.dg/pr86058.c @@ -1,8 +1,9 @@ /* PR middle-end/86058 - TARGET_MEM_REF causing incorrect message for -Wmaybe-uninitialized warning - { dg-do compile } + The test fails on a number of non-x86_64 targets due to pr100073. + { dg-do compile { target x86_64-*-* } } { dg-options "-O2 -Wuninitialized -Wmaybe-uninitialized" } */ - + extern void foo (int *); void zip (int *out, int indx) @@ -10,9 +11,9 @@ void zip (int *out, int indx) int arr[10]; for (int i = 0; i < indx; ++i) - out[i] = arr[i] + 1; // { dg-warning "'arr\\\[i]' may be used uninitialized" "pr?????" { xfail *-*-* } } + out[i] = arr[i] + 1; // { dg-warning "'arr\\\[i]' may be used uninitialized" "pr99944" { xfail *-*-* } } // { dg-warning "'arr' may be used uninitialized" "actual" { target *-*-* } .-1 } - + foo (arr); foo (out); }
reply other threads:[~2021-04-14 16:45 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=20210414164544.4EAF13851C2B@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: linkBe 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).