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++/58607] New: [4.9 Regression] ICE with undeclared variable in constexpr
Date: Thu, 03 Oct 2013 20:49:00 -0000	[thread overview]
Message-ID: <bug-58607-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 58607
           Summary: [4.9 Regression] ICE with undeclared variable in
                    constexpr
           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 (GCC 4.9.0 20130920):

=========================
struct A
{
  constexpr A() { i; }
};
=========================

bug.cc: In constructor 'constexpr A::A()':
bug.cc:3:19: error: 'i' was not declared in this scope
   constexpr A() { i; }
                   ^
bug.cc:3:22: internal compiler error: in build_data_member_initialization, at
cp/semantics.c:6032
   constexpr A() { i; }
                      ^
0x6c177e build_data_member_initialization
        ../../gcc/gcc/cp/semantics.c:6032
0x6c1cc9 build_constexpr_constructor_member_initializers
        ../../gcc/gcc/cp/semantics.c:6209
0x6c1cc9 massage_constexpr_body
        ../../gcc/gcc/cp/semantics.c:6290
0x6c94f3 register_constexpr_fundef(tree_node*, tree_node*)
        ../../gcc/gcc/cp/semantics.c:6394
0x568058 maybe_save_function_definition
        ../../gcc/gcc/cp/decl.c:13771
0x568058 finish_function(int)
        ../../gcc/gcc/cp/decl.c:13892
0x65090d cp_parser_function_definition_after_declarator
        ../../gcc/gcc/cp/parser.c:22346
0x635fbc cp_parser_late_parsing_for_member
        ../../gcc/gcc/cp/parser.c:22995
0x635fbc cp_parser_class_specifier_1
        ../../gcc/gcc/cp/parser.c:19078
0x638180 cp_parser_class_specifier
        ../../gcc/gcc/cp/parser.c:19102
0x638180 cp_parser_type_specifier
        ../../gcc/gcc/cp/parser.c:14081
0x64d679 cp_parser_decl_specifier_seq
        ../../gcc/gcc/cp/parser.c:11328
0x651719 cp_parser_simple_declaration
        ../../gcc/gcc/cp/parser.c:10918
0x653740 cp_parser_block_declaration
        ../../gcc/gcc/cp/parser.c:10867
0x65c76e cp_parser_declaration
        ../../gcc/gcc/cp/parser.c:10764
0x65b4da cp_parser_declaration_seq_opt
        ../../gcc/gcc/cp/parser.c:10650
0x65cda6 cp_parser_translation_unit
        ../../gcc/gcc/cp/parser.c:3939
0x65cda6 c_parse_file()
        ../../gcc/gcc/cp/parser.c:28900
0x7707e3 c_common_parse_file()
        ../../gcc/gcc/c-family/c-opts.c:1046
Please submit a full bug report, [etc.]


             reply	other threads:[~2013-10-03 20:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-03 20:49 reichelt at gcc dot gnu.org [this message]
2013-10-10 11:40 ` [Bug c++/58607] [4.9 Regression] [c++11] " rguenth at gcc dot gnu.org
2013-10-23  0:19 ` paolo.carlini at oracle dot com
2013-11-05 14:47 ` rguenth at gcc dot gnu.org
2013-11-25 20:52 ` paolo at gcc dot gnu.org
2013-11-25 20:53 ` 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-58607-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).