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++/102399] Cannot mix GCC and C++11 / C23 attribute syntax
Date: Sat, 04 Jun 2022 13:59:51 +0000	[thread overview]
Message-ID: <bug-102399-4-ESgqWKrJau@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102399-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 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:aec868578d8515763d75693c1fdfbc30ff0a1e68

commit r13-991-gaec868578d8515763d75693c1fdfbc30ff0a1e68
Author: Marek Polacek <polacek@redhat.com>
Date:   Thu Jun 2 15:44:20 2022 -0400

    c++: Allow mixing GNU/std-style attributes [PR69585]

    cp_parser_attributes_opt doesn't accept GNU attributes followed by
    [[]] attributes and vice versa; only a sequence of attributes of the
    same kind.  That causes grief for code like:

      struct __attribute__ ((may_alias)) alignas (2) struct S { };

    or

      #define EXPORT __attribute__((visibility("default")))
      struct [[nodiscard]] EXPORT F { };

    It doesn't seem to a documented restriction, so this patch fixes the
    problem.

    However, the patch does not touch the C FE.  The C FE doesn't have
    a counterpart to C++'s cp_parser_attributes_opt -- it only has
    c_parser_transaction_attributes (which parses both GNU and [[]]
    attributes), but that's TM-specific.  The C FE seems to use either
    c_parser_gnu_attributes or c_parser_std_attribute_specifier_sequence.
    As a consequence, this works:

      [[maybe_unused]] __attribute__((deprecated)) void f2 ();

    but this doesn't:

      __attribute__((deprecated)) [[maybe_unused]] void f1 ();

    I'm not sure what, if anything, should be done about this.

            PR c++/102399
            PR c++/69585

    gcc/cp/ChangeLog:

            * parser.cc (cp_parser_attributes_opt): Accept GNU attributes
            followed by [[]] attributes and vice versa.

    gcc/testsuite/ChangeLog:

            * g++.dg/ext/attrib65.C: New test.
            * g++.dg/ext/attrib66.C: New test.
            * g++.dg/ext/attrib67.C: New test.

      parent reply	other threads:[~2022-06-04 13:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-18 11:24 [Bug c++/102399] New: " dangelog at gmail dot com
2021-12-28  9:48 ` [Bug c++/102399] " pinskia at gcc dot gnu.org
2022-06-04 13:59 ` cvs-commit at gcc dot gnu.org [this message]

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-102399-4-ESgqWKrJau@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).