public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "foom at fuhm dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/100038] -Warray-bound triggers false positives Date: Thu, 10 Feb 2022 04:19:17 +0000 [thread overview] Message-ID: <bug-100038-4-UkKel9ML9n@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-100038-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100038 James Y Knight <foom at fuhm dot net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |foom at fuhm dot net --- Comment #8 from James Y Knight <foom at fuhm dot net> --- Here's a shorter test-case, reproduces with g++-11 -O2 -Warray-bounds: ``` struct SparseBitVectorElement { long Bits[2]; int find_first() const; }; int SparseBitVectorElement::find_first() const { for (unsigned i = 0; i < 2; ++i) if (Bits[i]) return i; // __builtin_unreachable(); // Illegal empty element } ``` The "__builtin_unreachable" at the end of the function seems to be the trigger for the issue -- presumably because the compiler decides to omit the loop end condition as being unnecessary. Trying the above on godbolt, it appears that it no longer occurs on gcc trunk for this test-case. But, I don't know if that was intentionally fixed or just happens not to trigger here. (I haven't tried compiling LLVM with a gcc trunk snapshot to see if all similar warnings have gone away.)
prev parent reply other threads:[~2022-02-10 4:19 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-11 17:47 [Bug c++/100038] New: " nicholas.stranchfield@you-spam.com 2021-04-11 19:51 ` [Bug middle-end/100038] " pinskia at gcc dot gnu.org 2021-04-11 20:47 ` nicholas.stranchfield@you-spam.com 2021-04-11 20:52 ` nicholas.stranchfield@you-spam.com 2021-04-11 20:53 ` nicholas.stranchfield@you-spam.com 2021-04-11 20:55 ` nicholas.stranchfield@you-spam.com 2021-04-11 20:56 ` nicholas.stranchfield@you-spam.com 2021-04-12 17:37 ` msebor at gcc dot gnu.org 2022-02-10 4:19 ` foom at fuhm dot net [this message]
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-100038-4-UkKel9ML9n@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).