public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dmalcolm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/106620] Incorrectly thinks execution can continue after a return statement
Date: Mon, 15 Aug 2022 15:33:50 +0000 [thread overview]
Message-ID: <bug-106620-4-vvbvMVkbSB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106620-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106620
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |WORKSFORME
--- Comment #1 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Thanks for filing this.
Looking at the Compiler Explorer link, the false positive occurs with gcc 11.1
at -O3.
With gcc 11.1 and gcc 11.3 the false +ve occurs at -O1 and above.
With gcc 12.1 and trunk, the false +ve does not occur.
I've made lots of implementation changes to -fanalyzer in gcc 12 in beyond that
I don't intend to backport to gcc 11, so I'm going to mark this as resolved
with "WORKSFORME".
Feel free to reopen it if you're able to reproduce it with gcc 12 or later;
thanks again for filing this.
next prev parent reply other threads:[~2022-08-15 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-15 8:55 [Bug analyzer/106620] New: " nrk at disroot dot org
2022-08-15 15:33 ` dmalcolm at gcc dot gnu.org [this message]
2022-08-15 15:34 ` [Bug analyzer/106620] " dmalcolm at gcc dot gnu.org
2022-08-16 2:06 ` nrk at disroot dot org
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-106620-4-vvbvMVkbSB@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: link
Be 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).