public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/107106] New: Incorrect use of uninitialized value warning
@ 2022-09-30 19:22 jlame646 at gmail dot com
2022-09-30 23:48 ` [Bug analyzer/107106] " dmalcolm at gcc dot gnu.org
2023-02-19 20:23 ` [Bug analyzer/107106] Incorrect use of uninitialized value warning on C++ jg at jguk dot org
0 siblings, 2 replies; 3+ messages in thread
From: jlame646 at gmail dot com @ 2022-09-30 19:22 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107106
Bug ID: 107106
Summary: Incorrect use of uninitialized value warning
Product: gcc
Version: 12.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: jlame646 at gmail dot com
Target Milestone: ---
The following program with `-fanalyzer` flag produces incorrect warning. Demo:
https://godbolt.org/z/YWd4cKbGc
```
#include <string>
std::string square(int num) {
return std::to_string(num * num);
}
```
The warning says:
```
<source>: In function 'std::string square(int)':
<source>:4:36: warning: use of uninitialized value '<unknown>' [CWE-457]
[-Wanalyzer-use-of-uninitialized-value]
4 | return std::to_string(num * num);
| ^
'std::string square(int)': events 1-2
|
| 3 | std::string square(int num) {
| | ^
| | |
| | (1) region created on stack here
| 4 | return std::to_string(num * num);
| | ~
| | |
| | (2) use of uninitialized value
'<unknown>' here
|
<source>:4:36: warning: use of uninitialized value '<unknown>' [CWE-457]
[-Wanalyzer-use-of-uninitialized-value]
4 | return std::to_string(num * num);
| ^
'std::string square(int)': events 1-2
|
| 3 | std::string square(int num) {
| | ^
| | |
| | (1) region created on stack here
| 4 | return std::to_string(num * num);
| | ~
| | |
| | (2) use of uninitialized value
'<unknown>' here
|
```
On searching for possible dupes, i came across this:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=13025 that may be related to this
bug.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug analyzer/107106] Incorrect use of uninitialized value warning
2022-09-30 19:22 [Bug c++/107106] New: Incorrect use of uninitialized value warning jlame646 at gmail dot com
@ 2022-09-30 23:48 ` dmalcolm at gcc dot gnu.org
2023-02-19 20:23 ` [Bug analyzer/107106] Incorrect use of uninitialized value warning on C++ jg at jguk dot org
1 sibling, 0 replies; 3+ messages in thread
From: dmalcolm at gcc dot gnu.org @ 2022-09-30 23:48 UTC (permalink / raw)
To: gcc-bugs
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug analyzer/107106] Incorrect use of uninitialized value warning on C++
2022-09-30 19:22 [Bug c++/107106] New: Incorrect use of uninitialized value warning jlame646 at gmail dot com
2022-09-30 23:48 ` [Bug analyzer/107106] " dmalcolm at gcc dot gnu.org
@ 2023-02-19 20:23 ` jg at jguk dot org
1 sibling, 0 replies; 3+ messages in thread
From: jg at jguk dot org @ 2023-02-19 20:23 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107106
Jonny Grant <jg at jguk dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jg at jguk dot org
--- Comment #2 from Jonny Grant <jg at jguk dot org> ---
I saw this and checked on latest trunk, just sharing as another test case.
If I have -Wno-analyzer-use-of-uninitialized-value it keeps this one quiet
<source>:7:12: warning: use of uninitialized value '<unknown>' [CWE-457]
[-Wanalyzer-use-of-uninitialized-value]
7 | return str;
#include <string>
std::string make_str(const char * str)
{
return str;
}
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-02-19 20:23 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-09-30 19:22 [Bug c++/107106] New: Incorrect use of uninitialized value warning jlame646 at gmail dot com
2022-09-30 23:48 ` [Bug analyzer/107106] " dmalcolm at gcc dot gnu.org
2023-02-19 20:23 ` [Bug analyzer/107106] Incorrect use of uninitialized value warning on C++ jg at jguk dot org
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).