public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "boris at kolpackov dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/98760] [modules] ICE in add_module_decl
Date: Thu, 04 Mar 2021 09:20:57 +0000 [thread overview]
Message-ID: <bug-98760-4-yl331U0bbb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98760-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98760
--- Comment #2 from Boris Kolpackov <boris at kolpackov dot net> ---
This still reproduces as of 11.0.1 20210304 (f3641ac70e) though the location
has changed:
hello.cxx:18:25: internal compiler error: in lookup_mark, at cp/tree.c:2403
18 | o << format_hello (n) << std::endl;
| ^
0xde6459 lookup_mark(tree_node*, bool)
../../gcc/gcc/cp/tree.c:2403
0xc5fb19 name_lookup::search_adl(tree_node*, vec<tree_node*, va_gc, vl_embed>*)
../../gcc/gcc/cp/name-lookup.c:1640
0xc5fff5 lookup_arg_dependent(tree_node*, tree_node*, vec<tree_node*, va_gc,
vl_embed>*)
../../gcc/gcc/cp/name-lookup.c:1740
0xdadd38 perform_koenig_lookup(cp_expr, vec<tree_node*, va_gc, vl_embed>*, int)
../../gcc/gcc/cp/semantics.c:2507
0xc92a1f cp_parser_postfix_expression
../../gcc/gcc/cp/parser.c:7658
0xc954c2 cp_parser_unary_expression
../../gcc/gcc/cp/parser.c:8818
0xc96bff cp_parser_cast_expression
../../gcc/gcc/cp/parser.c:9722
0xcc3a2c cp_parser_simple_cast_expression
../../gcc/gcc/cp/parser.c:30544
0xc9700f cp_parser_binary_expression
../../gcc/gcc/cp/parser.c:9890
0xc97c01 cp_parser_assignment_expression
../../gcc/gcc/cp/parser.c:10128
0xc97f6f cp_parser_expression
../../gcc/gcc/cp/parser.c:10298
0xc9be7c cp_parser_expression_statement
../../gcc/gcc/cp/parser.c:12012
0xc9b76a cp_parser_statement
../../gcc/gcc/cp/parser.c:11808
0xc9c42e cp_parser_statement_seq_opt
../../gcc/gcc/cp/parser.c:12159
0xc9c2fe cp_parser_compound_statement
../../gcc/gcc/cp/parser.c:12109
0xcb5719 cp_parser_function_body
../../gcc/gcc/cp/parser.c:24029
0xcb5a4c cp_parser_ctor_initializer_opt_and_function_body
../../gcc/gcc/cp/parser.c:24080
0xcc228e cp_parser_function_definition_after_declarator
../../gcc/gcc/cp/parser.c:29997
0xcc20a6 cp_parser_function_definition_from_specifiers_and_declarator
../../gcc/gcc/cp/parser.c:29913
0xcb0156 cp_parser_init_declarator
../../gcc/gcc/cp/parser.c:21602
next prev parent reply other threads:[~2021-03-04 9:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 7:26 [Bug c++/98760] New: " boris at kolpackov dot net
2021-01-20 7:27 ` [Bug c++/98760] " boris at kolpackov dot net
2021-03-04 9:20 ` boris at kolpackov dot net [this message]
2022-04-25 7:56 ` boris at kolpackov dot net
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-98760-4-yl331U0bbb@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).