public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mpolacek at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/95629] consteval operator== crashes compiler Date: Wed, 10 Jun 2020 22:52:48 +0000 [thread overview] Message-ID: <bug-95629-4-JYpM8KQ1xk@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95629-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95629 Marek Polacek <mpolacek at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mpolacek at gcc dot gnu.org Ever confirmed|0 |1 Keywords| |ice-on-valid-code Status|UNCONFIRMED |NEW Last reconfirmed| |2020-06-10 --- Comment #1 from Marek Polacek <mpolacek at gcc dot gnu.org> --- Thanks for the report. 95629.C: In function ‘int main()’: 95629.C:13:42: internal compiler error: in extract_call_expr, at cp/call.c:6634 13 | static_assert(hana<int>{} == hana<int>{}); | ^ 0x93ae4c extract_call_expr(tree_node*) /home/mpolacek/src/gcc/gcc/cp/call.c:6634 0x939f5a build_new_op_1 /home/mpolacek/src/gcc/gcc/cp/call.c:6335 0x93abb8 build_new_op(op_location_t const&, tree_code, int, tree_node*, tree_node*, tree_node*, tree_node**, int) /home/mpolacek/src/gcc/gcc/cp/call.c:6592 0xcb24b5 build_x_binary_op(op_location_t const&, tree_code, tree_node*, tree_code, tree_node*, tree_code, tree_node**, int) /home/mpolacek/src/gcc/gcc/cp/typeck.c:4280 0xb42759 cp_parser_binary_expression /home/mpolacek/src/gcc/gcc/cp/parser.c:9777 0xb42c12 cp_parser_assignment_expression /home/mpolacek/src/gcc/gcc/cp/parser.c:9914 0xb43462 cp_parser_constant_expression /home/mpolacek/src/gcc/gcc/cp/parser.c:10208 0xb4d16e cp_parser_static_assert /home/mpolacek/src/gcc/gcc/cp/parser.c:14741 0xb4b0ff cp_parser_block_declaration /home/mpolacek/src/gcc/gcc/cp/parser.c:13608 0xb4a594 cp_parser_declaration_statement /home/mpolacek/src/gcc/gcc/cp/parser.c:13217 0xb4651c cp_parser_statement /home/mpolacek/src/gcc/gcc/cp/parser.c:11523 0xb47230 cp_parser_statement_seq_opt /home/mpolacek/src/gcc/gcc/cp/parser.c:11889 0xb47114 cp_parser_compound_statement /home/mpolacek/src/gcc/gcc/cp/parser.c:11839 0xb5d175 cp_parser_function_body /home/mpolacek/src/gcc/gcc/cp/parser.c:23115 0xb5d499 cp_parser_ctor_initializer_opt_and_function_body /home/mpolacek/src/gcc/gcc/cp/parser.c:23166 0xb69008 cp_parser_function_definition_after_declarator /home/mpolacek/src/gcc/gcc/cp/parser.c:29062 0xb68e2f cp_parser_function_definition_from_specifiers_and_declarator /home/mpolacek/src/gcc/gcc/cp/parser.c:28978 0xb58384 cp_parser_init_declarator /home/mpolacek/src/gcc/gcc/cp/parser.c:20721 0xb4b57c cp_parser_simple_declaration /home/mpolacek/src/gcc/gcc/cp/parser.c:13785 0xb4b11e cp_parser_block_declaration /home/mpolacek/src/gcc/gcc/cp/parser.c:13611
next prev parent reply other threads:[~2020-06-10 22:52 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-10 21:38 [Bug c++/95629] New: " tobias.bruell at gmail dot com 2020-06-10 22:52 ` mpolacek at gcc dot gnu.org [this message] 2020-06-10 22:57 ` [Bug c++/95629] " iains at gcc dot gnu.org 2020-06-14 18:04 ` johelegp at gmail dot com 2020-06-23 15:42 ` mpolacek at gcc dot gnu.org 2020-06-28 23:00 ` mpolacek at gcc dot gnu.org
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-95629-4-JYpM8KQ1xk@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: linkBe 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).