public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gscfq@t-online.de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/108438] New: [10/11/12/13 Regression] ICE in cxx_eval_constant_expression, at cp/constexpr.cc:7611 Date: Tue, 17 Jan 2023 17:53:34 +0000 [thread overview] Message-ID: <bug-108438-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108438 Bug ID: 108438 Summary: [10/11/12/13 Regression] ICE in cxx_eval_constant_expression, at cp/constexpr.cc:7611 Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: gscfq@t-online.de Target Milestone: --- Started with r6 and -Wall : $ cat z1.cc template <typename T> T foo (T arg, T& ref, T* ptr) { int a = 1; return static_cast<T!>(a); } $ g++-13-20230115 -c z1.cc -Wall z1.cc: In function 'T foo(T, T&, T*)': z1.cc:5:23: error: expected '>' before '!' token 5 | return static_cast<T!>(a); | ^ z1.cc:5:23: error: expected '(' before '!' token 5 | return static_cast<T!>(a); | ^ | ( z1.cc:5:24: error: expected primary-expression before '>' token 5 | return static_cast<T!>(a); | ^ z1.cc:5:27: internal compiler error: in cxx_eval_constant_expression, at cp/constexpr.cc:7611 5 | return static_cast<T!>(a); | ^ 0x883b61 cxx_eval_constant_expression ../../gcc/cp/constexpr.cc:7611 0x88c97a cxx_eval_outermost_constant_expr ../../gcc/cp/constexpr.cc:8252 0x891e42 maybe_constant_value(tree_node*, tree_node*, bool) ../../gcc/cp/constexpr.cc:8527 0xa11806 cp_parser_binary_expression ../../gcc/cp/parser.cc:10233 0xa11da4 cp_parser_assignment_expression ../../gcc/cp/parser.cc:10444 0xa14362 cp_parser_expression ../../gcc/cp/parser.cc:10614 0xa2b843 cp_parser_postfix_expression ../../gcc/cp/parser.cc:7356 0xa44ddf cp_parser_unary_expression ../../gcc/cp/parser.cc:9095 0xa106ef cp_parser_cast_expression ../../gcc/cp/parser.cc:9999 0xa1101f cp_parser_binary_expression ../../gcc/cp/parser.cc:10101 0xa11da4 cp_parser_assignment_expression ../../gcc/cp/parser.cc:10444 0xa14362 cp_parser_expression ../../gcc/cp/parser.cc:10614 0xa27806 cp_parser_jump_statement ../../gcc/cp/parser.cc:14359 0xa27806 cp_parser_statement ../../gcc/cp/parser.cc:12335 0xa27de4 cp_parser_statement_seq_opt ../../gcc/cp/parser.cc:12909 0xa27ec7 cp_parser_compound_statement ../../gcc/cp/parser.cc:12861 0xa51d90 cp_parser_function_body ../../gcc/cp/parser.cc:25280 0xa51d90 cp_parser_ctor_initializer_opt_and_function_body ../../gcc/cp/parser.cc:25331 0xa5240a cp_parser_function_definition_after_declarator ../../gcc/cp/parser.cc:31953 0xa5393c cp_parser_function_definition_from_specifiers_and_declarator ../../gcc/cp/parser.cc:31870
next reply other threads:[~2023-01-17 17:53 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-17 17:53 gscfq@t-online.de [this message] 2023-01-17 21:00 ` [Bug c++/108438] " mpolacek at gcc dot gnu.org 2023-01-18 9:00 ` rguenth at gcc dot gnu.org 2023-07-07 10:44 ` [Bug c++/108438] [11/12/13/14 " rguenth at gcc dot gnu.org 2024-06-07 9:05 ` [Bug c++/108438] [11/12/13/14/15 " simartin at gcc dot gnu.org 2024-06-08 11:13 ` cvs-commit at gcc dot gnu.org 2024-06-08 11:15 ` simartin at gcc dot gnu.org 2024-06-08 14:53 ` sjames 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-108438-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: 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).