public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "reichelt at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/59270] New: [4.9 Regression] [c++11] ICE with decltype of a broken class
Date: Sat, 23 Nov 2013 23:26:00 -0000	[thread overview]
Message-ID: <bug-59270-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59270

            Bug ID: 59270
           Summary: [4.9 Regression] [c++11] ICE with decltype of a broken
                    class
           Product: gcc
           Version: 4.9.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: reichelt at gcc dot gnu.org

The following invalid code snippet (compiled with "-std=c++11") triggers an ICE
on trunk:

====================
struct A
{
  struct B b;
};

decltype(A()) a;
====================

bug.cc:3:12: error: field 'b' has incomplete type 'B'
   struct B b;
            ^
bug.cc:6:12: internal compiler error: tree check: expected class 'type', have
'exceptional' (error_mark) in type_build_ctor_call, at cp/class.c:5163
 decltype(A()) a;
            ^
0xd5dc85 tree_class_check_failed(tree_node const*, tree_code_class, char
const*, int, char const*)
        ../../gcc/gcc/tree.c:9243
0x614ed6 tree_class_check
        ../../gcc/gcc/tree.h:2831
0x614ed6 type_build_ctor_call(tree_node*)
        ../../gcc/gcc/cp/class.c:5163
0x6bcdb7 build_value_init(tree_node*, int)
        ../../gcc/gcc/cp/init.c:339
0x6bc9ef build_value_init_noctor(tree_node*, int)
        ../../gcc/gcc/cp/init.c:412
0x6bce4c build_value_init(tree_node*, int)
        ../../gcc/gcc/cp/init.c:364
0x606e6b build_functional_cast(tree_node*, tree_node*, int)
        ../../gcc/gcc/cp/typeck2.c:1858
0x66c0b5 cp_parser_functional_cast
        ../../gcc/gcc/cp/parser.c:23013
0x666930 cp_parser_postfix_expression
        ../../gcc/gcc/cp/parser.c:5821
0x6675ec cp_parser_decltype_expr
        ../../gcc/gcc/cp/parser.c:11833
0x6675ec cp_parser_decltype
        ../../gcc/gcc/cp/parser.c:11932
0x67eb57 cp_parser_simple_type_specifier
        ../../gcc/gcc/cp/parser.c:14462
0x65f29d cp_parser_type_specifier
        ../../gcc/gcc/cp/parser.c:14309
0x67634f cp_parser_decl_specifier_seq
        ../../gcc/gcc/cp/parser.c:11476
0x67ce69 cp_parser_simple_declaration
        ../../gcc/gcc/cp/parser.c:11066
0x660e03 cp_parser_block_declaration
        ../../gcc/gcc/cp/parser.c:11015
0x6875a6 cp_parser_declaration
        ../../gcc/gcc/cp/parser.c:10912
0x686298 cp_parser_declaration_seq_opt
        ../../gcc/gcc/cp/parser.c:10798
0x687b6a cp_parser_translation_unit
        ../../gcc/gcc/cp/parser.c:4018
0x687b6a c_parse_file()
        ../../gcc/gcc/cp/parser.c:31259
Please submit a full bug report, [etc.]


             reply	other threads:[~2013-11-23 23:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-23 23:26 reichelt at gcc dot gnu.org [this message]
2013-11-25  9:16 ` [Bug c++/59270] " rguenth at gcc dot gnu.org
2014-01-15 10:52 ` paolo.carlini at oracle dot com
2014-01-15 10:58 ` ktkachov at gcc dot gnu.org
2014-01-15 11:00 ` paolo.carlini at oracle dot com
2014-01-15 11:30 ` ktkachov at gcc dot gnu.org
2014-01-17 20:25 ` paolo at gcc dot gnu.org
2014-01-17 20:26 ` paolo.carlini at oracle dot com

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-59270-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).