public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Kito Cheng <kito@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-1357] testsuite/102690: Only check warning for lp64 in Warray-bounds-16.C Date: Thu, 30 Jun 2022 02:15:11 +0000 (GMT) [thread overview] Message-ID: <20220630021511.668EF3852744@sourceware.org> (raw) https://gcc.gnu.org/g:0f6eef398045deb2a62d18b526831719c7c20c8a commit r13-1357-g0f6eef398045deb2a62d18b526831719c7c20c8a Author: Kito Cheng <kito.cheng@sifive.com> Date: Tue Jun 28 18:43:42 2022 +0800 testsuite/102690: Only check warning for lp64 in Warray-bounds-16.C That warning won't happen on ilp32 targets, seems like Andrew Pinski already mention that[1] before. Verified on riscv32-unknown-elf and riscv64-unknown-elf. [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92879#c1 gcc/testsuite/ChangeLog: PR testsuite/102690 * g++.dg/warn/Warray-bounds-16.C: XFAIL only on lp64 for the warning. Diff: --- gcc/testsuite/g++.dg/warn/Warray-bounds-16.C | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/testsuite/g++.dg/warn/Warray-bounds-16.C b/gcc/testsuite/g++.dg/warn/Warray-bounds-16.C index 89cbadb91c7..45a14b19ea3 100644 --- a/gcc/testsuite/g++.dg/warn/Warray-bounds-16.C +++ b/gcc/testsuite/g++.dg/warn/Warray-bounds-16.C @@ -19,7 +19,7 @@ struct S p = (int*) new unsigned char [sizeof (int) * m]; for (int i = 0; i < m; i++) - new (p + i) int (); /* { dg-bogus "bounds" "pr102690" { xfail *-*-* } } */ + new (p + i) int (); /* { dg-bogus "bounds" "pr102690" { xfail lp64 } } */ } };
reply other threads:[~2022-06-30 2:15 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=20220630021511.668EF3852744@sourceware.org \ --to=kito@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).