public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/66214] New: [6 Regression] ICE verify_type failed with -O0 -g via gen_type_die_with_usage's dwarf2out.c:20250
Date: Wed, 20 May 2015 11:16:00 -0000 [thread overview]
Message-ID: <bug-66214-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66214
Bug ID: 66214
Summary: [6 Regression] ICE verify_type failed with -O0 -g via
gen_type_die_with_usage's dwarf2out.c:20250
Product: gcc
Version: 6.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: middle-end
Assignee: unassigned at gcc dot gnu.org
Reporter: burnus at gcc dot gnu.org
CC: hubicka at gcc dot gnu.org
Target Milestone: ---
Created attachment 35574
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35574&action=edit
Test case (input13.ii): Compile with g++ -std=c++11 -g
The bug reminds me of 66103, but is one is without LTO.
Compiling the attached code snipped with "g++ -std=c++11 -g" give the following
ICE. Without "-g", it doesn't crash:
input13.ii:53:34: required from here
input13.ii:44:74: error: TYPE_CANONICAL is not compatible
template < typename _Tp, typename _Alloc = std::allocator < _Tp > >class
vector:protected _Vector_base < _Tp,
[...]
input13.ii:44:74: internal compiler error: verify_type failed
0xf3e280 verify_type(tree_node const*)
../../gcc/tree.c:13257
0x96dc04 gen_type_die_with_usage
../../gcc/dwarf2out.c:20250
0x96e2a3 gen_type_die_with_usage
../../gcc/dwarf2out.c:20337
0x97f21c gen_type_die
../../gcc/dwarf2out.c:20434
0x97f21c gen_formal_types_die
../../gcc/dwarf2out.c:18027
next reply other threads:[~2015-05-20 11:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 11:16 burnus at gcc dot gnu.org [this message]
2015-05-20 11:17 ` [Bug middle-end/66214] " burnus at gcc dot gnu.org
2015-05-20 13:10 ` mpolacek at gcc dot gnu.org
2015-05-22 8:19 ` burnus at gcc dot gnu.org
2015-05-26 12:13 ` burnus at gcc dot gnu.org
2015-05-27 6:47 ` burnus at gcc dot gnu.org
2015-06-08 11:54 ` trippels at gcc dot gnu.org
2015-06-10 15:06 ` trippels at gcc dot gnu.org
2015-06-11 21:53 ` hubicka at gcc dot gnu.org
2015-07-06 11:44 ` burnus at gcc dot gnu.org
2015-08-02 3:46 ` jim at meyering dot net
2015-08-10 11:52 ` burnus at gcc dot gnu.org
2015-08-12 23:07 ` anton at samba dot org
2015-08-28 17:23 ` trippels at gcc dot gnu.org
2015-09-20 4:58 ` trippels at gcc dot gnu.org
2015-10-16 22:35 ` gcc at magfr dot user.lysator.liu.se
2015-10-21 19:53 ` gcc at magfr dot user.lysator.liu.se
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-66214-4@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).