public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hubicka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/66214] [6 Regression] ICE verify_type failed with -O0 -g via gen_type_die_with_usage's dwarf2out.c:20250
Date: Thu, 11 Jun 2015 21:53:00 -0000 [thread overview]
Message-ID: <bug-66214-4-ZLDSnGHsap@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66214-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66214
Jan Hubicka <hubicka at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jason at redhat dot com
--- Comment #8 from Jan Hubicka <hubicka at gcc dot gnu.org> ---
Jaon,
the issue here is that TYPE_CANONICAL is incomplete type:
<record_type 0x3fff8e94c8d0 A readonly type_5 VOID
align 8 symtab 0 alias set -1 canonical type 0x3fff8e94c8d0 context
<translation_unit_decl 0x3fff96fc0078 D.1>
full-name "const class A"
n_parents=0 use_template=0 interface-unknown reference_to_this
<reference_type 0x3fff8e94ca20>>
while the type itself is complete (it is a completetion of the class A provided
later):
<record_type 0x3fff8e94d158 value_type readonly used type_5 VOID
align 8 symtab -1903885616 alias set -1 canonical type 0x3fff8e94c8d0
fields <field_decl 0x3fff8e834c00 m_upperBorder
type <integer_type 0x3fff8e770690 int public type_6 SI
size <integer_cst 0x3fff8e7316b0 constant 32>
unit size <integer_cst 0x3fff8e7316c8 constant 4>
align 32 symtab 0 alias set -1 canonical type 0x3fff8e770690
precision 32 min <integer_cst 0x3fff8e731668 -2147483648> max <integer_cst
0x3fff8e731680 2147483647>
pointer_to_this <pointer_type 0x3fff8e7717a0>>
private decl_3 VOID file t.C line 7 col 7
align 1 offset_align 1 context <record_type 0x3fff8e94c4e0 A>
chain <type_decl 0x3fff8e834b68 A type <record_type 0x3fff8e94ceb8 A>
nonlocal decl_4 VOID file t.C line 6 col 9
align 1 context <record_type 0x3fff8e94c4e0 A> result <record_type
0x3fff8e94c4e0 A>
>> context <translation_unit_decl 0x3fff96fc0078 D.1>
full-name "const value_type"
n_parents=0 use_template=0 interface-unknown reference_to_this
<reference_type 0x3fff8e94d200>>
Shouldn't the canonical type be always the complete variant of the type?
next prev parent reply other threads:[~2015-06-11 21:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 11:16 [Bug middle-end/66214] New: " burnus at gcc dot gnu.org
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 [this message]
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-ZLDSnGHsap@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).