public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Christophe Lyon <clyon@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-382] testsuite: Make AArch64 attributes_7.c generate unique report lines. Date: Fri, 13 May 2022 08:03:22 +0000 (GMT) [thread overview] Message-ID: <20220513080322.E6189384B000@sourceware.org> (raw) https://gcc.gnu.org/g:bac63f1ea9121a59e980981cfb8b2ea1869f12f0 commit r13-382-gbac63f1ea9121a59e980981cfb8b2ea1869f12f0 Author: Christophe Lyon <christophe.lyon@arm.com> Date: Fri May 6 18:30:51 2022 +0100 testsuite: Make AArch64 attributes_7.c generate unique report lines. This test is executed in both C and C++ modes, lines 98 and 100 pass in C++ and are xfail in C. This results in similar lines in gcc.sum and g++.sum, differing by the PASS or XFAIL prefix, which confuses compare_test: it reports these tests twice, as "now fail, but worked before" and "now work, but didn't before". To make the diagnostic different betweek C and C++, I use $tool in the dg-error comment field. 2022-05-13 Christophe Lyon <christophe.lyon@arm.com> gcc/testsuite/ * gcc.target/aarch64/sve/acle/general/attributes_7.c: Make diagnostic unique. Diff: --- gcc/testsuite/gcc.target/aarch64/sve/acle/general/attributes_7.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gcc/testsuite/gcc.target/aarch64/sve/acle/general/attributes_7.c b/gcc/testsuite/gcc.target/aarch64/sve/acle/general/attributes_7.c index 621666ce6c9..95be60591fb 100644 --- a/gcc/testsuite/gcc.target/aarch64/sve/acle/general/attributes_7.c +++ b/gcc/testsuite/gcc.target/aarch64/sve/acle/general/attributes_7.c @@ -95,9 +95,9 @@ f (int c) fb = sb; (void) (c ? sb : sb); - (void) (c ? sb : fb); // { dg-error {type mismatch|different types} "" { xfail c } } + (void) (c ? sb : fb); // { dg-error {type mismatch|different types} "$tool" { xfail c } } - (void) (c ? fb : sb); // { dg-error {type mismatch|different types} "" { xfail c } } + (void) (c ? fb : sb); // { dg-error {type mismatch|different types} "$tool" { xfail c } } (void) (c ? fb : fb); }
reply other threads:[~2022-05-13 8:03 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=20220513080322.E6189384B000@sourceware.org \ --to=clyon@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).