public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/114472] [14 Regression] ICE: in falls_short_of_p, at analyzer/store.cc:365 (in exceeds_p, at analyzer/store.cc:342) with -fanalyzer
Date: Wed, 10 Apr 2024 20:47:19 +0000	[thread overview]
Message-ID: <bug-114472-4-69QwimZtgR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114472-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by David Malcolm <dmalcolm@gcc.gnu.org>:

https://gcc.gnu.org/g:4a94551d7eaaf7a75c5195fc0bf4af94185a04c7

commit r14-9902-g4a94551d7eaaf7a75c5195fc0bf4af94185a04c7
Author: David Malcolm <dmalcolm@redhat.com>
Date:   Wed Apr 10 16:43:30 2024 -0400

    analyzer: fix ICE on negative values for size_t [PR114472]

    I made several attempts to fix this properly, but for now apply
    a band-aid to at least prevent crashing on such cases.

    gcc/analyzer/ChangeLog:
            PR analyzer/114472
            * access-diagram.cc (bit_size_expr::maybe_get_formatted_str):
            Reject attempts to print sizes that are too large.
            * region.cc (region_offset::calc_symbolic_bit_offset): Use a
            typeless svalue for the bit offset.
            * store.cc (bit_range::intersects_p): Replace assertion with
            test.
            (bit_range::exceeds_p): Likewise.
            (bit_range::falls_short_of_p): Likewise.

    gcc/testsuite/ChangeLog:
            * c-c++-common/analyzer/out-of-bounds-pr114472.c: New test.

    Signed-off-by: David Malcolm <dmalcolm@redhat.com>

  parent reply	other threads:[~2024-04-10 20:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-25 18:25 [Bug analyzer/114472] New: " zsojka at seznam dot cz
2024-03-25 18:47 ` [Bug analyzer/114472] " dmalcolm at gcc dot gnu.org
2024-03-26  8:06 ` rguenth at gcc dot gnu.org
2024-04-09 11:41 ` jakub at gcc dot gnu.org
2024-04-09 20:06 ` dmalcolm at gcc dot gnu.org
2024-04-10 20:47 ` cvs-commit at gcc dot gnu.org [this message]
2024-04-10 21:00 ` 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-114472-4-69QwimZtgR@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).