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/104062] [12 Regression] ICE in get_or_create_cast, at analyzer/region-model-manager.cc:482 since r12-6476-g4f34f8cc1d064bfa
Date: Tue, 18 Jan 2022 20:56:05 +0000 [thread overview]
Message-ID: <bug-104062-4-2utSrP1fKt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-104062-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104062
--- Comment #3 from CVS 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:79e746bb05e432dcd1c18161469272d67c33d79d
commit r12-6699-g79e746bb05e432dcd1c18161469272d67c33d79d
Author: David Malcolm <dmalcolm@redhat.com>
Date: Tue Jan 18 10:03:53 2022 -0500
analyzer: fix ICE on realloc of zeroed memory [PR104062]
gcc/analyzer/ChangeLog:
PR analyzer/104062
* region-model-manager.cc
(region_model_manager::maybe_fold_sub_svalue): Avoid casting to
NULL type when folding access to repeated svalue.
gcc/testsuite/ChangeLog:
PR analyzer/104062
* gcc.dg/analyzer/pr104062.c: New test.
Signed-off-by: David Malcolm <dmalcolm@redhat.com>
next prev parent reply other threads:[~2022-01-18 20:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-17 9:21 [Bug analyzer/104062] New: [12 Regression] ICE in get_or_create_cast, at analyzer/region-model-manager.cc:482 asolokha at gmx dot com
2022-01-17 9:51 ` [Bug analyzer/104062] " rguenth at gcc dot gnu.org
2022-01-17 10:47 ` [Bug analyzer/104062] [12 Regression] ICE in get_or_create_cast, at analyzer/region-model-manager.cc:482 since r12-6476-g4f34f8cc1d064bfa marxin at gcc dot gnu.org
2022-01-18 15:04 ` dmalcolm at gcc dot gnu.org
2022-01-18 20:56 ` cvs-commit at gcc dot gnu.org [this message]
2022-01-18 20:59 ` 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-104062-4-2utSrP1fKt@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).