public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Dimitar Dimitrov <dimitar@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r13-215] testsuite: Silence analyzer/pr51628-30.c for default_packed Date: Mon, 9 May 2022 16:33:12 +0000 (GMT) [thread overview] Message-ID: <20220509163312.A1F0D3858D32@sourceware.org> (raw) https://gcc.gnu.org/g:8a39c7c128dbf4405821778724c5a1017ab12e06 commit r13-215-g8a39c7c128dbf4405821778724c5a1017ab12e06 Author: Dimitar Dimitrov <dimitar@dinux.eu> Date: Fri Apr 22 18:22:00 2022 +0300 testsuite: Silence analyzer/pr51628-30.c for default_packed On default_packed targets like PRU, a warning in the file included from analyzer/pr51628-30.c is reported as spurious one, even though it has been annotated there: Excess errors: gcc/gcc/testsuite/gcc.dg/analyzer/torture/../../../c-c++-common/pr51628-30.c:7:19: warning: 'packed' attribute ignored for field of type 'struct B' [-Wattributes] Mark that gcc.dg/analyzer/torture/pr51628-30.c generates excess warnings for default_packed targets. This is safe because the original test case covered an ICE, not a diagnostic error. gcc/testsuite/ChangeLog: * gcc.dg/analyzer/torture/pr51628-30.c: Test can spill excess errors for default_packed targets. Signed-off-by: Dimitar Dimitrov <dimitar@dinux.eu> Diff: --- gcc/testsuite/gcc.dg/analyzer/torture/pr51628-30.c | 1 + 1 file changed, 1 insertion(+) diff --git a/gcc/testsuite/gcc.dg/analyzer/torture/pr51628-30.c b/gcc/testsuite/gcc.dg/analyzer/torture/pr51628-30.c index 4513e0f890c..abc13413f2b 100644 --- a/gcc/testsuite/gcc.dg/analyzer/torture/pr51628-30.c +++ b/gcc/testsuite/gcc.dg/analyzer/torture/pr51628-30.c @@ -1,3 +1,4 @@ /* { dg-additional-options "-Wno-address-of-packed-member" } */ +/* { dg-excess-errors "warnings about ignored 'packed' attribute" { target default_packed } } */ #include "../../../c-c++-common/pr51628-30.c"
reply other threads:[~2022-05-09 16:33 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=20220509163312.A1F0D3858D32@sourceware.org \ --to=dimitar@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).