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/111305] [13/14 Regression] GCC Static Analyzer -Wanalyzer-out-of-bounds false postive
Date: Mon, 18 Mar 2024 22:53:46 +0000	[thread overview]
Message-ID: <bug-111305-4-AWr1uncjuC@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111305-4@http.gcc.gnu.org/bugzilla/>

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P2                          |P3
            Summary|[13/14 Regression] GCC      |[13/14 Regression] GCC
                   |Static Analyzer             |Static Analyzer
                   |-Wanalyzer-out-of-bounds FP |-Wanalyzer-out-of-bounds
                   |and ICE problem             |false postive

--- Comment #4 from David Malcolm <dmalcolm at gcc dot gnu.org> ---
ICE should be fixed by the above patch.

False positive still not fixed.

  parent reply	other threads:[~2024-03-18 22:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-06 12:18 [Bug analyzer/111305] New: GCC Static Analyzer -Wanalyzer-out-of-bounds FP and ICE problem geoffreydgr at icloud dot com
2024-02-26 22:30 ` [Bug analyzer/111305] [13/14 Regression] " dmalcolm at gcc dot gnu.org
2024-03-04 13:01 ` rguenth at gcc dot gnu.org
2024-03-07 23:21 ` law at gcc dot gnu.org
2024-03-12 13:25 ` jakub at gcc dot gnu.org
2024-03-18 22:47 ` cvs-commit at gcc dot gnu.org
2024-03-18 22:53 ` dmalcolm at gcc dot gnu.org [this message]
2024-03-22 13:39 ` [Bug analyzer/111305] [13/14 Regression] GCC Static Analyzer -Wanalyzer-out-of-bounds false postive law at gcc dot gnu.org
2024-05-21  9:17 ` [Bug analyzer/111305] [13/14/15 " jakub 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-111305-4-AWr1uncjuC@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).