public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/91027] [10 regression] SEGV in hash_table<odr_name_hasher, false, xcallocator>::find_slot_with_hash
Date: Wed, 25 Mar 2020 11:49:58 +0000 [thread overview]
Message-ID: <bug-91027-4-YXceeNALlx@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-91027-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91027
Rainer Orth <ro at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|FIXED |---
Status|RESOLVED |REOPENED
--- Comment #14 from Rainer Orth <ro at gcc dot gnu.org> ---
Unfortunately, the bug is not fixed: while the original SEGV doesn't happen any
longer, I now see the ICE originally reported in Comment #6 on both
i386-pc-solaris2.11
and sparc-sun-solaris2.11:
FAIL: gdc.dg/lto/ltotests d_lto_ltotests_0.o-d_lto_ltotests_1.o link, -O0 -flto
-flto-partition=none (internal compiler error)
during IPA pass: pure-const^M
lto1: internal compiler error: in get_odr_type, at ipa-devirt.c:1936^M
0x7c4dfb get_odr_type(tree_node*, bool)^M
/vol/gcc/src/hg/master/local/gcc/ipa-devirt.c:1936^M
0x7cba63 build_type_inheritance_graph()^M
/vol/gcc/src/hg/master/local/gcc/ipa-devirt.c:2283^M
0x822f83 symbol_table::remove_unreachable_nodes(__FILE*)^M
/vol/gcc/src/hg/master/local/gcc/ipa.c:320^M
0x476fd7 read_cgraph_and_symbols(unsigned int, char const**)^M
/vol/gcc/src/hg/master/local/gcc/lto/lto-common.c:2915^M
0x459043 lto_main()^M
/vol/gcc/src/hg/master/local/gcc/lto/lto.c:625^M
next prev parent reply other threads:[~2020-03-25 11:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-91027-4@http.gcc.gnu.org/bugzilla/>
2020-03-17 19:11 ` ibuclaw at gdcproject dot org
2020-03-20 16:26 ` cvs-commit at gcc dot gnu.org
2020-03-20 16:28 ` ibuclaw at gcc dot gnu.org
2020-03-25 11:49 ` ro at gcc dot gnu.org [this message]
2020-04-01 17:13 ` ibuclaw at gdcproject dot org
2020-04-01 17:14 ` ibuclaw at gdcproject dot org
2020-04-01 17:16 ` ibuclaw at gdcproject dot org
2020-04-02 8:34 ` ro at CeBiTec dot Uni-Bielefeld.DE
2020-04-02 8:34 ` ro 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-91027-4-YXceeNALlx@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).