public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/98969] [11 Regression] ICE: Segmentation fault (in print_mem_ref)
Date: Fri, 05 Feb 2021 08:15:24 +0000 [thread overview]
Message-ID: <bug-98969-4-QCKa8VPbQy@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98969-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98969
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dmalcolm at gcc dot gnu.org
Component|c |analyzer
--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
The bug is in the analyzer which builds a MEM_REF with non-pointer argument
zero here:
#0 0x000000000194ce94 in build2 (code=MEM_REF,
tt=<record_type 0x7ffff669ed20 TYPE_14__>,
arg0=<ssa_name 0x7ffff6575d38 2>, arg1=<integer_cst 0x7ffff66b0138>)
at /home/rguenther/src/gcc3/gcc/tree.c:4876
#1 0x0000000001ac2f7e in ana::region_model::get_representative_path_var (
this=0x3b27a30, reg=0x3b237c0, visited=0x7fffffffc6c0)
at /home/rguenther/src/gcc3/gcc/analyzer/region-model.cc:2319
#2 0x0000000001ac303d in ana::region_model::get_representative_path_var (
this=0x3b27a30, reg=0x3b23800, visited=0x7fffffffc6c0)
at /home/rguenther/src/gcc3/gcc/analyzer/region-model.cc:2334
(gdb) l
2314 const svalue *pointer = symbolic_reg->get_pointer ();
2315 path_var pointer_pv = get_representative_path_var (pointer,
visited);
2316 if (!pointer_pv)
2317 return path_var (NULL_TREE, 0);
2318 tree offset = build_int_cst (pointer->get_type (), 0);
2319 return path_var (build2 (MEM_REF,
2320 reg->get_type (),
2321 pointer_pv.m_tree,
2322 offset),
2323 pointer_pv.m_stack_depth);
next prev parent reply other threads:[~2021-02-05 8:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-04 17:06 [Bug c/98969] New: " asolokha at gmx dot com
2021-02-04 20:34 ` [Bug c/98969] " msebor at gcc dot gnu.org
2021-02-04 20:50 ` msebor at gcc dot gnu.org
2021-02-04 20:52 ` jakub at gcc dot gnu.org
2021-02-05 8:15 ` rguenth at gcc dot gnu.org [this message]
2021-02-05 14:08 ` [Bug analyzer/98969] " jakub at gcc dot gnu.org
2021-02-05 14:18 ` dmalcolm at gcc dot gnu.org
2021-02-06 16:16 ` msebor at gcc dot gnu.org
2021-02-06 17:10 ` msebor at gcc dot gnu.org
2021-02-11 1:59 ` dmalcolm at gcc dot gnu.org
2021-02-12 1:32 ` cvs-commit at gcc dot gnu.org
2021-02-12 1:36 ` dmalcolm at gcc dot gnu.org
2021-02-17 15:38 ` cvs-commit at gcc dot gnu.org
2021-02-17 15: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-98969-4-QCKa8VPbQy@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).