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/97130] [11 Regression] ICE in deref_rvalue, at analyzer/region-model.cc:1462
Date: Mon, 21 Sep 2020 22:51:12 +0000 [thread overview]
Message-ID: <bug-97130-4-x7yJae8DWA@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97130-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97130
--- Comment #2 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:1e19ecd79b45af6df87a6869d1936b857c9f71fc
commit r11-3341-g1e19ecd79b45af6df87a6869d1936b857c9f71fc
Author: David Malcolm <dmalcolm@redhat.com>
Date: Mon Sep 21 11:59:26 2020 -0400
analyzer: fix ICE on bogus decl of memset [PR97130]
Verify that arguments are pointers before calling handling code
that calls deref_rvalue on them.
gcc/analyzer/ChangeLog:
PR analyzer/97130
* region-model-impl-calls.cc (call_details::get_arg_type): New.
* region-model.cc (region_model::on_call_pre): Check that the
initial arg is a pointer before calling impl_call_memset and
impl_call_strlen.
* region-model.h (call_details::get_arg_type): New decl.
gcc/testsuite/ChangeLog:
PR analyzer/97130
* gcc.dg/analyzer/pr97130.c: New test.
next prev parent reply other threads:[~2020-09-21 22:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-21 4:41 [Bug analyzer/97130] New: " asolokha at gmx dot com
2020-09-21 6:56 ` [Bug analyzer/97130] " rguenth at gcc dot gnu.org
2020-09-21 16:07 ` dmalcolm at gcc dot gnu.org
2020-09-21 22:51 ` cvs-commit at gcc dot gnu.org [this message]
2020-09-21 22:55 ` 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-97130-4-x7yJae8DWA@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).