From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 15BD13858405; Sun, 15 May 2022 19:34:50 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 15BD13858405
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:34:50 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 9.1.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: iains at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-93082-4-mUXu0myw1d@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-93082-4@http.gcc.gnu.org/bugzilla/>
References: <bug-93082-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Sun, 15 May 2022 19:34:51 -0000

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

--- Comment #10 from Iain Sandoe <iains at gcc dot gnu.org> ---
I also have a few "clang compatibility workarounds" for GCC (including one =
for
this specific case) - but they need putting behind some "-fclang-compatibil=
ity"
flag or so.

Hopefully, will work on integrating them in GCC-13.

In some cases that is going to work better than a fix includes.

FWIW this is not actually a bug in GCC, the bug is in the headers as Andrew
points out (the value is valid in C++ but not for C):

" Funny how clang thinks this was an GNU extension when it is not one."

I do not currently have a plan to try and build a second fix includes tree =
for
Frameworks, but happy to review patches if someone else does :)=