public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Hans-Peter Nilsson <hp@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-5251] gcc.dg/uninit-pred-9_b.c: Correct last adjustment for cris-elf Date: Mon, 15 Nov 2021 06:59:41 +0000 (GMT) [thread overview] Message-ID: <20211115065941.DF4443858D39@sourceware.org> (raw) https://gcc.gnu.org/g:adcfd2c45c3523d74279b5fcac1d7c6c34dd1382 commit r12-5251-gadcfd2c45c3523d74279b5fcac1d7c6c34dd1382 Author: Hans-Peter Nilsson <hp@axis.com> Date: Mon Nov 15 07:50:44 2021 +0100 gcc.dg/uninit-pred-9_b.c: Correct last adjustment for cris-elf The change at r12-4790 should have done the same change for CRIS as was done for powerpc64*-*-*. (Probably MMIX too but that may have to wait until the next weekend.) gcc/testsuite: * gcc.dg/uninit-pred-9_b.c: Correct last adjustment, for CRIS. Diff: --- gcc/testsuite/gcc.dg/uninit-pred-9_b.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gcc/testsuite/gcc.dg/uninit-pred-9_b.c b/gcc/testsuite/gcc.dg/uninit-pred-9_b.c index 552ab8b4ff4..53c4a5399ea 100644 --- a/gcc/testsuite/gcc.dg/uninit-pred-9_b.c +++ b/gcc/testsuite/gcc.dg/uninit-pred-9_b.c @@ -17,10 +17,10 @@ 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*-*-* } } */ + blah(v); /* { dg-bogus "uninitialized" "bogus warning" { xfail powerpc64*-*-* cris-*-* } } */ if ( (n <= 8) && (m < 99) && (r < 19) ) - blah(v); /* { dg-bogus "uninitialized" "pr101674" { xfail mmix-*-* cris-*-* } } */ + blah(v); /* { dg-bogus "uninitialized" "pr101674" { xfail mmix-*-* } } */ return 0; }
reply other threads:[~2021-11-15 6:59 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=20211115065941.DF4443858D39@sourceware.org \ --to=hp@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).