public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/100401] Bogus -Wformat-overflow for a trailing zero-length array of a union Date: Mon, 03 May 2021 19:30:58 +0000 [thread overview] Message-ID: <bug-100401-4-2EjJVci4cu@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100401-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100401 Martin Sebor <msebor at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail| |10.2.0, 11.1.0 Summary|Bogus -Wformat-overflow |Bogus -Wformat-overflow for |warning |a trailing zero-length | |array of a union CC| |msebor at gcc dot gnu.org Status|UNCONFIRMED |NEW Component|c |middle-end Last reconfirmed| |2021-05-03 Ever confirmed|0 |1 --- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> --- Confirmed with GCC 10. The warning is avoided in GCC 11 (since r11-5622). The change is too intrusive to backport and it's seems that the warning doesn't trigger anymore might be incidental to it. It can still be reproduced on trunk but only in C++. I would suggest to expect warnings for tricks like in the test case (writing past subobject boundaries). GCC warnings are designed to "report constructions that are not inherently erroneous but that are risky or suggest there may have been an error." Access warnings like -Warray-bounds, -Wformat-overflow, and -Wstringop-overflow try to accommodate code they have been taught is likely safe but the logic is secondary to helping find bugs, and not foolproof.
next prev parent reply other threads:[~2021-05-03 19:30 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-03 16:58 [Bug c/100401] New: Bogus -Wformat-overflow warning lavr at ncbi dot nlm.nih.gov 2021-05-03 19:30 ` msebor at gcc dot gnu.org [this message] 2021-05-03 20:09 ` [Bug middle-end/100401] Bogus -Wformat-overflow for a trailing zero-length array of a union lavr at ncbi dot nlm.nih.gov
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=bug-100401-4-2EjJVci4cu@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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).