public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug middle-end/70765] GCC fails to detect possibly uninitialized variable
[not found] <bug-70765-4@http.gcc.gnu.org/bugzilla/>
@ 2021-04-12 20:32 ` msebor at gcc dot gnu.org
0 siblings, 0 replies; only message in thread
From: msebor at gcc dot gnu.org @ 2021-04-12 20:32 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70765
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |diagnostic
Resolution|--- |WONTFIX
CC| |msebor at gcc dot gnu.org
Status|UNCONFIRMED |RESOLVED
--- Comment #4 from Martin Sebor <msebor at gcc dot gnu.org> ---
-Wuninitialized, -Wmaybe-uninitialized, and all other flow-sensitive warnings
depend on optimization (including inlining) to avoid both false positives and
false negatives. This is one of the many cases that's only detectable thanks
to optimization. GCC's static analyzer might be able to do better in GCC 12
(if/when -Wanalyzer-use-of-uninitialized-value becomes supported). Thus
resolving as WONTFIX.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2021-04-12 20:32 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-70765-4@http.gcc.gnu.org/bugzilla/>
2021-04-12 20:32 ` [Bug middle-end/70765] GCC fails to detect possibly uninitialized variable msebor at gcc dot gnu.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).