public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/98969] [11 Regression] ICE: Segmentation fault (in print_mem_ref)
Date: Thu, 04 Feb 2021 20:34:02 +0000 [thread overview]
Message-ID: <bug-98969-4-zlvbHF4MOK@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
Martin Sebor <msebor at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
CC| |msebor at gcc dot gnu.org
Last reconfirmed| |2021-02-04
--- Comment #1 from Martin Sebor <msebor at gcc dot gnu.org> ---
Confirmed. The ICE is in accessing arg_type in the snippet below when it's
null.
tree arg_type = TREE_TYPE (TREE_TYPE (arg));
...
/* True to include a cast to the accessed type. */
const bool access_cast
= ((op && op != TREE_OPERAND (arg, 0))
|| VOID_TYPE_P (arg_type)
|| !lang_hooks.types_compatible_p (access_type, arg_type));
const bool has_off = byte_off != 0 || (op && op != TREE_OPERAND (arg, 0));
arg is set to the integer but the arg_type initalizer assumes it's a pointer:
<ssa_name 0x7fffea802d38
type <integer_type 0x7fffea810738 long int public DI
size <integer_cst 0x7fffea7f7cd8 constant 64>
unit-size <integer_cst 0x7fffea7f7cf0 constant 8>
align:64 warn_if_not_align:0 symtab:0 alias-set -1 canonical-type
0x7fffea810738 precision:64 min <integer_cst 0x7fffea7f7f60
-9223372036854775808> max <integer_cst 0x7fffea7f7f78 9223372036854775807>
pointer_to_this <pointer_type 0x7fffea820150>>
visited var <parm_decl 0x7fffea950080 _round_2_cb_n_0>
def_stmt GIMPLE_NOP
version:2>
next prev parent reply other threads:[~2021-02-04 20:34 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 ` msebor at gcc dot gnu.org [this message]
2021-02-04 20:50 ` [Bug c/98969] " msebor at gcc dot gnu.org
2021-02-04 20:52 ` jakub at gcc dot gnu.org
2021-02-05 8:15 ` [Bug analyzer/98969] " rguenth at gcc dot gnu.org
2021-02-05 14:08 ` 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-zlvbHF4MOK@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).