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 target/93082] macOS Authorization.h needs fixinclude
Date: Sun, 15 May 2022 19:44:36 +0000	[thread overview]
Message-ID: <bug-93082-4-KVlzCfVFV9@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-93082-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #11 from Iain Sandoe <iains at gcc dot gnu.org> ---
Created attachment 52980
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=52980&action=edit
work in progress patch for this case

 * this is not finished (needs to be conditional on a compatibility flag)
 * might not be acceptable upstream (depending on whether other maintainers are
willing to accept clang extension work-arounds). 

However, AFAICS this 'extension' would affect all targets if they were
presented with such input (so that this is not actually a Darwin-specific
problem) - it's just that we see it in the headers.

The patch is against recent master, but I'd expect it to apply reasonably
easily to 12.1, 11.3 and 10.x.

  parent reply	other threads:[~2022-05-15 19:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-93082-4@http.gcc.gnu.org/bugzilla/>
2020-11-24 18:28 ` grobian at gentoo dot org
2020-11-27 21:36 ` mcccs at gmx dot com
2020-11-27 23:18 ` sam at gentoo dot org
2021-11-12 15:30 ` egallager at gcc dot gnu.org
2022-05-14 23:28 ` egallager at gcc dot gnu.org
2022-05-15 19:25 ` bkorb at gnu dot org
2022-05-15 19:26 ` bkorb at gnu dot org
2022-05-15 19:34 ` iains at gcc dot gnu.org
2022-05-15 19:44 ` iains at gcc dot gnu.org [this message]
2022-05-24 14:27 ` egallager at gcc dot gnu.org
2022-05-24 15:14 ` egallager at gcc dot gnu.org
2023-01-06  8:23 ` sam at gentoo dot 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-93082-4-KVlzCfVFV9@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).