public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/97159] segfault in modref_may_conflict
Date: Tue, 22 Sep 2020 09:38:19 +0000 [thread overview]
Message-ID: <bug-97159-4-QzcY2HgWM9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-97159-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97159
--- Comment #1 from Tom de Vries <vries at gcc dot gnu.org> ---
Segfaults because tt is NULL:
...
Program received signal SIGSEGV, Segmentation fault.
0x00000000012b1a69 in modref_may_conflict (tt=0x0, ref=0x7fffffffd8d0,
tbaa_p=true)
at /home/vries/oacc/trunk/source-gcc/gcc/tree-ssa-alias.c:2433
2433 if (tt->every_base)
(gdb)
...
tt comes from summary->loads:
...
(gdb) up
#1 0x00000000012b1da1 in ref_maybe_used_by_call_p_1 (call=0x7ffff7ff43f0,
ref=0x7fffffffd8d0, tbaa_p=true)
at /home/vries/oacc/trunk/source-gcc/gcc/tree-ssa-alias.c:2513
2513 if (!modref_may_conflict (summary->loads, ref, tbaa_p))
...
and summary looks like:
...
(gdb) p *summary
$2 = {loads = 0x0, stores = 0x0, loads_lto = 0x0, stores_lto = 0x0, finished =
true}
...
next prev parent reply other threads:[~2020-09-22 9:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 9:34 [Bug tree-optimization/97159] New: " vries at gcc dot gnu.org
2020-09-22 9:38 ` vries at gcc dot gnu.org [this message]
2020-09-22 9:47 ` [Bug tree-optimization/97159] " vries at gcc dot gnu.org
2020-09-22 10:51 ` [Bug tree-optimization/97159] [11 Regression] " rguenth at gcc dot gnu.org
2020-09-22 19:57 ` Jan Hubicka
2020-09-22 19:57 ` hubicka at ucw dot cz
2020-10-05 7:17 ` vries at gcc dot gnu.org
2020-10-06 8:18 ` vries 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-97159-4-QzcY2HgWM9@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).