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++/108607] New: [12/13 Regression] ICE in potential_constant_expression_1, at cp/constexpr.cc:10003
Date: Mon, 30 Jan 2023 20:09:40 +0000	[thread overview]
Message-ID: <bug-108607-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108607

            Bug ID: 108607
           Summary: [12/13 Regression] ICE in
                    potential_constant_expression_1, at
                    cp/constexpr.cc:10003
           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 between 20210808 and 20210822 :


$ cat z1.cc
constexpr int bar (int x);
constexpr int foo (int x)
{
  [[omp::directive (scope nowait)]]
  return bar (x);
}


$ g++-13-20230129 -c z1.cc -fopenmp
z1.cc: In function 'constexpr int foo(int)':
z1.cc:5:16: error: invalid exit from OpenMP structured block
    5 |   return bar (x);
      |                ^
z1.cc:6:1: sorry, unimplemented: unexpected AST of kind omp_scope
    6 | }
      | ^
z1.cc:6:1: internal compiler error: in potential_constant_expression_1, at
cp/constexpr.cc:10003
0x893ef0 potential_constant_expression_1
        ../../gcc/cp/constexpr.cc:10003
0x89536a potential_constant_expression_1(tree_node*, bool, bool, bool, bool,
int)
        ../../gcc/cp/constexpr.cc:10027
0x896166 potential_rvalue_constant_expression(tree_node*)
        ../../gcc/cp/constexpr.cc:10047
0x896166 maybe_save_constexpr_fundef(tree_node*)
        ../../gcc/cp/constexpr.cc:959
0x926a31 finish_function(bool)
        ../../gcc/cp/decl.cc:18204
0xa64e03 cp_parser_function_definition_after_declarator
        ../../gcc/cp/parser.cc:31998
0xa6633c cp_parser_function_definition_from_specifiers_and_declarator
        ../../gcc/cp/parser.cc:31912
0xa6633c cp_parser_init_declarator
        ../../gcc/cp/parser.cc:22777
0xa36572 cp_parser_simple_declaration
        ../../gcc/cp/parser.cc:15390
0xa6dd1b cp_parser_declaration
        ../../gcc/cp/parser.cc:15076
0xa6e838 cp_parser_translation_unit
        ../../gcc/cp/parser.cc:5131
0xa6e838 c_parse_file()
        ../../gcc/cp/parser.cc:49472
0xc169e1 c_common_parse_file()
        ../../gcc/c-family/c-opts.cc:1248

             reply	other threads:[~2023-01-30 20:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-30 20:09 gscfq@t-online.de [this message]
2023-01-31  8:52 ` [Bug c++/108607] " rguenth at gcc dot gnu.org
2023-01-31 16:01 ` jakub at gcc dot gnu.org
2023-02-01  9:43 ` cvs-commit at gcc dot gnu.org
2023-02-01  9:45 ` [Bug c++/108607] [12 " jakub at gcc dot gnu.org
2023-02-10 17:46 ` cvs-commit at gcc dot gnu.org
2023-02-10 18:01 ` jakub at gcc dot gnu.org
2023-05-02 20:14 ` cvs-commit at gcc dot gnu.org
2023-05-03 15:21 ` cvs-commit 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-108607-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).