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/107106] Incorrect use of uninitialized value warning
Date: Fri, 30 Sep 2022 23:48:17 +0000 [thread overview]
Message-ID: <bug-107106-4-VEORnS6Emf@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107106-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107106
David Malcolm <dmalcolm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
Last reconfirmed| |2022-09-30
Blocks| |97110
--- Comment #1 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Thanks for filing this bug; confirmed.
Note that the simpler:
std::string square(int num) {
return std::to_string(num);
}
also gives the warning.
Note that I recommend *not* using -fanalyzer on C++ code for now; see tracker
bug 97110. I'm guessing the issue is due to -fanalyzer failing to cope with
exceptions and exception-handling (bug 97111). In the meantime, this is a test
case that we'll eventually want to get working, so keeping open.
Referenced Bugs:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97110
[Bug 97110] [meta-bug] tracker bug for supporting C++ in -fanalyzer
next prev parent reply other threads:[~2022-09-30 23:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-30 19:22 [Bug c++/107106] New: " jlame646 at gmail dot com
2022-09-30 23:48 ` dmalcolm at gcc dot gnu.org [this message]
2023-02-19 20:23 ` [Bug analyzer/107106] Incorrect use of uninitialized value warning on C++ jg at jguk 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-107106-4-VEORnS6Emf@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).