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 E657A38417FE; Tue, 13 Dec 2022 10:24:46 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E657A38417FE
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1670927086;
	bh=M63oHwbFPEZ3FJyRGlC/9nG+I8UirGSGa9GsNy66gdE=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=FAll3ZSHXM0X/I0ZPTuxkkdmwVbuvtcB7P42K5cPK0ufYCbOv4BQJ0kwWLzKOGGBS
	 V59fnrG0gK3sEBqbknYypw8yE0vwvWlZOYH6APzJRyxP2oRoOWjnKxUlFP42my+DTe
	 II/nla3TYQdYDEUci2MFJJ65AWkQrUR/G33K1lD4=
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/107568] Bootstrap failure on macOS 12.6 (monterey)
Date: Tue, 13 Dec 2022 10:24:39 +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: 13.0
X-Bugzilla-Keywords: build
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-107568-4-w5posRzqSu@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-107568-4@http.gcc.gnu.org/bugzilla/>
References: <bug-107568-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
List-Id: <gcc-bugs.sourceware.org>

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

--- Comment #6 from Iain Sandoe <iains at gcc dot gnu.org> ---
since this effects upstream *-*-darwin21+ the bug is now tracked here (I've
closed the arm64 duvet branch dup)

I am considering amending the darwin host module to add
-Wno-error=3Ddeprecated-declarations to the STAGE2+ flags, rather than
fix-including.

Two reasons:
 * fixincludes make life tricky when compiling for different Darwin versions
with --sysroot (since they leak into the target runtime, esp. libstdc++
headers).  It's better to avoid them if possible

 * fixinclude-ing would make the GCC behaviour different from clang's on
end-user's code. It is clear that Apple's intention is dissuade users from =
the
unsafer APIs (which is reasonable, I guess, but the mechanism is a bit
heavy-handed).

anyway just thoughts at present, no draft patch yet.=