public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/103539] [C++23] P2324 - Labels at the end of compound statements
Date: Mon, 09 May 2022 19:57:24 +0000	[thread overview]
Message-ID: <bug-103539-4-E5ImfAGYZZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-103539-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The trunk branch has been updated by Marek Polacek <mpolacek@gcc.gnu.org>:

https://gcc.gnu.org/g:4b2a6628644b2ce15d877c1e85d14e314965a296

commit r13-217-g4b2a6628644b2ce15d877c1e85d14e314965a296
Author: Marek Polacek <polacek@redhat.com>
Date:   Sun May 8 17:36:34 2022 -0400

    c++: Implement P2324R2, labels at the end of compound-stmts [PR103539]

    This patch implements C++23 <https://wg21.link/p2324r2>, which allows
    labels at the end of a compound statement.   Its C FE counterpart was
    already implemented in r11-4813.

    In cp_parser_statement I rely on in_compound to determine whether we're
    in a compound-statement, so that the patch doesn't accidentally allow

      void fn(int c) {
        if (c)
      label:
      }

    Strangely, in_compound was reset after seeing a label (this is tested in
    c-c++-common/gomp/pr63326.c), so I've made a modifiable copy specific
    for OpenMP #pragma purposes.

            PR c++/103539

    gcc/cp/ChangeLog:

            * parser.cc (cp_parser_statement): Constify the in_compound
parameter.
            Create a modifiable copy.  Allow labels at the end of compound
            statements.

    gcc/testsuite/ChangeLog:

            * g++.dg/cpp23/label1.C: New test.
            * g++.dg/cpp23/label2.C: New test.

  parent reply	other threads:[~2022-05-09 19:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-03 14:04 [Bug c++/103539] New: " mpolacek at gcc dot gnu.org
2021-12-03 14:05 ` [Bug c++/103539] " mpolacek at gcc dot gnu.org
2022-05-09 19:57 ` cvs-commit at gcc dot gnu.org [this message]
2022-05-09 20:02 ` 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-103539-4-E5ImfAGYZZ@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).