public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dangelog at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/102399] New: Cannot mix GCC and C++11 / C23 attribute syntax
Date: Sat, 18 Sep 2021 11:24:48 +0000	[thread overview]
Message-ID: <bug-102399-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 102399
           Summary: Cannot mix GCC and C++11 / C23 attribute syntax
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dangelog at gmail dot com
  Target Milestone: ---

Hello,

If one tries to mix GCC's attribute syntax (__attribute__) and with C++11 / C23
([[attribute]]), GCC rejects the code (no matter what the order of the
attributes is):


  #define EXPORT __attribute__((visibility("default")))

  struct [[nodiscard]] EXPORT Foo { Foo(); };


https://gcc.godbolt.org/z/W868xjeMq


While a workaround exists (by sticking to the same "kind" of attribute syntax),
it's not always possible or easy to achieve in big codebases, where for
compatibility/legacy reasons the attributes are expanded via macros and can
expand to a random combination of GCC or C++ attributes.

For comparison, Clang and MSVC allow mixed syntaxes.

             reply	other threads:[~2021-09-18 11:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-18 11:24 dangelog at gmail dot com [this message]
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

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@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).