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] Many -Wanalyzer-use-of-uninitialized-value false positives seen in qemu's softfloat.c
Date: Wed, 08 Feb 2023 18:58:29 +0000	[thread overview]
Message-ID: <bug-108704-4-dyWH5hKEQH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108704-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108704

David Malcolm <dmalcolm at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|[13 Regression] Many        |Many
                   |-Wanalyzer-use-of-uninitial |-Wanalyzer-use-of-uninitial
                   |ized-value false positives  |ized-value false positives
                   |seen in qemu's softfloat.c  |seen in qemu's softfloat.c

--- Comment #4 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
Should be fixed on trunk for GCC 13 by the above commit.

I introduced the bug in r12-7718-gfaacafd2306ad7 so in theory it affects GCC 12
as well, but I haven't been able to reproduce it there.  The bug is probably
present there but latent, so I'm keeping this bug open to track backporting the
fix to the gcc 12 branch.

  parent reply	other threads:[~2023-02-08 18:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07 23:13 [Bug analyzer/108704] New: " dmalcolm at gcc dot gnu.org
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 ` dmalcolm at gcc dot gnu.org [this message]
2023-03-29 18:19 ` [Bug analyzer/108704] " 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-dyWH5hKEQH@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).