[Bug c++/59200] New: ICE with invalid alias template use
redi at gcc dot gnu.org
gcc-bugzilla@gcc.gnu.org
Wed Nov 20 03:41:00 GMT 2013
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59200
Bug ID: 59200
Summary: ICE with invalid alias template use
Product: gcc
Version: 4.9.0
Status: UNCONFIRMED
Keywords: ice-on-invalid-code
Severity: normal
Priority: P3
Component: c++
Assignee: unassigned at gcc dot gnu.org
Reporter: redi at gcc dot gnu.org
struct A
{
static constexpr bool value = true;
};
template<typename T>
struct B
{
template<typename U>
using C = A;
};
template<typename T>
template<typename U>
const bool B<T>::C<U>::value;
$ g++ -std=gnu++11 -c t.cc
t.cc:15:23: internal compiler error: in cp_parser_type_name, at
cp/parser.c:14692
const bool B<T>::C<U>::value;
^
0x63918c cp_parser_type_name
/home/jwakely/src/gcc/gcc/cp/parser.c:14692
0x6293ce cp_parser_qualifying_entity
/home/jwakely/src/gcc/gcc/cp/parser.c:5535
0x6293ce cp_parser_nested_name_specifier_opt
/home/jwakely/src/gcc/gcc/cp/parser.c:5244
0x629d3f cp_parser_nested_name_specifier
/home/jwakely/src/gcc/gcc/cp/parser.c:5443
0x629e88 cp_parser_ptr_operator
/home/jwakely/src/gcc/gcc/cp/parser.c:17469
0x62c484 cp_parser_declarator
/home/jwakely/src/gcc/gcc/cp/parser.c:16818
0x64053d cp_parser_init_declarator
/home/jwakely/src/gcc/gcc/cp/parser.c:16417
0x64141e cp_parser_single_declaration
/home/jwakely/src/gcc/gcc/cp/parser.c:22914
0x6416c4 cp_parser_template_declaration_after_export
/home/jwakely/src/gcc/gcc/cp/parser.c:22716
0x6419d5 cp_parser_template_declaration_after_export
/home/jwakely/src/gcc/gcc/cp/parser.c:22702
0x6204a1 cp_parser_declaration
/home/jwakely/src/gcc/gcc/cp/parser.c:10852
0x64d959 cp_parser_declaration_seq_opt
/home/jwakely/src/gcc/gcc/cp/parser.c:10782
0x64de09 cp_parser_translation_unit
/home/jwakely/src/gcc/gcc/cp/parser.c:4010
0x64de09 c_parse_file()
/home/jwakely/src/gcc/gcc/cp/parser.c:31187
0x77d4d4 c_common_parse_file()
/home/jwakely/src/gcc/gcc/c-family/c-opts.c:1055
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.
See <http://gcc.gnu.org/bugs.html> for instructions.
More information about the Gcc-bugs
mailing list