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] Support for clang-style attributes is needed to parse Darwin SDK headers properly
Date: Tue, 16 May 2023 19:37:09 +0000	[thread overview]
Message-ID: <bug-109877-4-hrcIMnRSPB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-109877-4@http.gcc.gnu.org/bugzilla/>

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

Iain Sandoe <iains at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |90709
           Assignee|unassigned at gcc dot gnu.org      |iains at gcc dot gnu.org
             Status|UNCONFIRMED                 |NEW
     Ever confirmed|0                           |1
           Severity|normal                      |enhancement
   Last reconfirmed|                            |2023-05-16

--- Comment #1 from Iain Sandoe <iains at gcc dot gnu.org> ---
I have a working draft for c-family (I do not know if D and M2 are interested
in attributes)


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90709
[Bug 90709] [meta-bug] GNU Objective C (C++) cannot consume current headers on
Darwin platforms.

  reply	other threads:[~2023-05-16 19:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-16 19:35 [Bug c++/109877] New: " iains at gcc dot gnu.org
2023-05-16 19:37 ` iains at gcc dot gnu.org [this message]
2023-05-16 19:39 ` [Bug c++/109877] " 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-hrcIMnRSPB@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).