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: Wed, 17 May 2023 07:33:23 +0000	[thread overview]
Message-ID: <bug-109877-4-eMh1RDtejI@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

--- Comment #8 from Iain Sandoe <iains at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #7)
> can we fixinclude the headers?

1. not yet (PR105719) - although let us hope we can find a way to do that for
more limited cases (I've implemented the consumer code, but the generation and
install side is more work).

2. In any event, (especially for 'availability') that would be a huge job
(essentially re-writing a significant bunch of framework and /usr/include
cases), and keeping up with frequent Xcode / SDK updates would be quite a
maintenance burden***.

3. It does not help our downstream to use other projects which make use of
these features (in non-SDK sources).

----

*** other options considered:

for "closed" SDKs for system versions out of vendor support, I suppose we could
just have a script that sed'ed the headers into a replacement, but that is
still some machinery to implement.

It would be nice to have an open SDK - but that is a huge project in its own
right, and likewise would need someone with time to maintain the bleeding edge
version

      parent reply	other threads:[~2023-05-17  7:33 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 ` [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 [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-109877-4-eMh1RDtejI@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).