public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/109877] New: Support for clang-style attributes is needed to parse Darwin SDK headers properly Date: Tue, 16 May 2023 19:35:07 +0000 [thread overview] Message-ID: <bug-109877-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109877 Bug ID: 109877 Summary: Support for clang-style attributes is needed to parse Darwin SDK headers properly Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: iains at gcc dot gnu.org Target Milestone: --- clang has GNU-style attribute support, but with essentially per-attribute parsing of the attribute argument list. This extends to, for example: __attribute__((availability(macOS, introduced=12.3.4))) and: __attribute__((availability(macOS, message="partial string" "more string"))) These are examples that GCC rejects; The issue actually need addressing during lexing since the first is an invalid token for a number (it's intended to represent a version) and we reject it before the parser has a chance to treat it specially. Ergo, we need a way to escape clang-specific attributes so that we can parse them.
next reply other threads:[~2023-05-16 19:35 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-05-16 19:35 iains at gcc dot gnu.org [this message] 2023-05-16 19:37 ` [Bug c++/109877] " iains at gcc dot gnu.org 2023-05-16 19:39 ` pinskia at gcc dot gnu.org 2023-05-16 19:50 ` iains at gcc dot gnu.org 2023-05-16 20:00 ` jakub at gcc dot gnu.org 2023-05-16 20:08 ` iains at gcc dot gnu.org 2023-05-16 20:26 ` jakub at gcc dot gnu.org 2023-05-17 7:09 ` rguenth at gcc dot gnu.org 2023-05-17 7:33 ` iains 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-109877-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).