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/108704] New: Many -Wanalyzer-use-of-uninitialized-value false positives seen in qemu's softfloat.c Date: Tue, 07 Feb 2023 23:13:14 +0000 [thread overview] Message-ID: <bug-108704-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108704 Bug ID: 108704 Summary: Many -Wanalyzer-use-of-uninitialized-value false positives seen in qemu's softfloat.c Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: analyzer Assignee: dmalcolm at gcc dot gnu.org Reporter: dmalcolm at gcc dot gnu.org Target Milestone: --- Created attachment 54425 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=54425&action=edit Reduced reproducer Trunk shows many (dozens?) of -Wanalyzer-use-of-uninitialized-value false positives on qemu's softfloat.c https://godbolt.org/z/MTe9597Eh shows: <source>: In function 'test': <source>:27:9: warning: use of uninitialized value 'fp0' [CWE-457] [-Wanalyzer-use-of-uninitialized-value] 27 | fp0 = floatx80_add(fp0, float32_to_floatx80((0x3F800000))); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 'test': events 1-3 | | 24 | floatx80 fp0; | | ^~~ | | | | | (1) region created on stack here | | (2) capacity: 16 bytes |...... | 27 | fp0 = floatx80_add(fp0, float32_to_floatx80((0x3F800000))); | | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | | | | | (3) use of uninitialized value 'fp0' here | Compiler returned: 0 where fp0 appears to have been initialized on the line above.
next reply other threads:[~2023-02-07 23:13 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-02-07 23:13 dmalcolm at gcc dot gnu.org [this message] 2023-02-07 23:14 ` [Bug analyzer/108704] [13 Regression] " dmalcolm at gcc dot gnu.org 2023-02-07 23:30 ` dmalcolm at gcc dot gnu.org 2023-02-08 18:48 ` cvs-commit at gcc dot gnu.org 2023-02-08 18:58 ` [Bug analyzer/108704] " dmalcolm at gcc dot gnu.org 2023-03-29 18:19 ` cvs-commit at gcc dot gnu.org 2023-03-29 19:31 ` dmalcolm at gcc dot gnu.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-108704-4@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).