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/96646] [11 Regression] ICE: Segmentation fault (in tree_class_check)
Date: Sat, 26 Sep 2020 01:34:05 +0000	[thread overview]
Message-ID: <bug-96646-4-C5RO1HocTa@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-96646-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 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:29f5db8ef81fac4db8e66e5f06fdf1d469e8161c

commit r11-3471-g29f5db8ef81fac4db8e66e5f06fdf1d469e8161c
Author: David Malcolm <dmalcolm@redhat.com>
Date:   Fri Sep 25 17:15:42 2020 -0400

    analyzer: fix ICEs treeifying offset_region [PR96646, PR96841]

    gcc/analyzer/ChangeLog:
            PR analyzer/96646
            PR analyzer/96841
            * region-model.cc (region_model::get_representative_path_var):
            When handling offset_region, wrap the MEM_REF's first argument in
            an ADDR_EXPR of pointer type, rather than simply using the tree
            for the parent region.  Require the MEM_REF's second argument to
            be an integer constant.

    gcc/testsuite/ChangeLog:
            PR analyzer/96646
            PR analyzer/96841
            * gcc.dg/analyzer/pr96646.c: New test.
            * gcc.dg/analyzer/pr96841.c: New test.

  parent reply	other threads:[~2020-09-26  1:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-17  8:57 [Bug analyzer/96646] New: " asolokha at gmx dot com
2020-08-25 10:31 ` [Bug analyzer/96646] " rguenth at gcc dot gnu.org
2020-09-26  1:34 ` cvs-commit at gcc dot gnu.org [this message]
2020-09-26  1:40 ` 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-96646-4-C5RO1HocTa@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).