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/100011] [11 Regression] ICE in analyzer when generating path for -Wanalyzer-unsafe-call-within-signal-handler
Date: Sat, 10 Apr 2021 20:24:00 +0000 [thread overview]
Message-ID: <bug-100011-4-hPjckiyIzM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100011-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100011
--- 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:ec633d3777bd71f7bde5e671b61ec18e5b7b43ea
commit r11-8117-gec633d3777bd71f7bde5e671b61ec18e5b7b43ea
Author: David Malcolm <dmalcolm@redhat.com>
Date: Sat Apr 10 16:23:23 2021 -0400
analyzer: fix ICE on assignment from STRING_CST when building path
[PR100011]
gcc/analyzer/ChangeLog:
PR analyzer/100011
* region-model.cc (region_model::on_assignment): Avoid NULL
dereference if ctxt is NULL when assigning from a STRING_CST.
gcc/testsuite/ChangeLog:
PR analyzer/100011
* gcc.dg/analyzer/pr100011.c: New test.
next prev parent reply other threads:[~2021-04-10 20:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 2:35 [Bug analyzer/100011] New: internal compiler error in analyzer during IPA pass raj.khem at gmail dot com
2021-04-10 2:38 ` [Bug analyzer/100011] " raj.khem at gmail dot com
2021-04-10 15:46 ` [Bug analyzer/100011] [11 Regression] ICE in analyzer when generating path for -Wanalyzer-unsafe-call-within-signal-handler dmalcolm at gcc dot gnu.org
2021-04-10 20:24 ` cvs-commit at gcc dot gnu.org [this message]
2021-04-10 20:24 ` dmalcolm at gcc dot gnu.org
2021-04-12 10:03 ` acoplan 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-100011-4-hPjckiyIzM@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).