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 41A353858420; Thu, 22 Feb 2024 13:28:01 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 41A353858420
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1708608481;
	bh=nqLE92X+3DBIrq6vohrgiRDNsegbzlKXnj5mzkFuNyU=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=enZDnwJOaN2AacWkiEt0FMRv/Zlk8imOyV4zllkLWhd+iRRG/jhdICT5C9IT9sa50
	 pd/akQe7v6jwjadQWseADS7d8XOnTAAVcAH3tUqKcfNPWK3rOzstkY7Iq58Jht7JCe
	 ui8TY/+4Dps9sZGdeg63cMTFuMAP6S68pnT86QOA=
From: "ro at CeBiTec dot Uni-Bielefeld.DE" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114049] gcc.dg/framework-1.c FAILs with Xcode 15.3 beta
 3
Date: Thu, 22 Feb 2024 13:28:01 +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: 14.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: ro at CeBiTec dot Uni-Bielefeld.DE
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 14.0
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-114049-4-4VTC5fHIQr@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-114049-4@http.gcc.gnu.org/bugzilla/>
References: <bug-114049-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=3D114049

--- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot U=
ni-Bielefeld.DE> ---
> --- Comment #3 from Iain Sandoe <iains at gcc dot gnu.org> ---
> so .. if i follow your discussion correctly - neither clang nor gcc finds=
 it
> because it's incorrectly quoted (is that an SDK issue?).. or?

The quoting is one part, certainly.  While clang falls back from <> to
"", gcc does not.  However, even if I change string.h locally to use "",
while this allows machine/trap.h to be found, the subsequent i386/trap.h
is still not found, neither by gcc nor by clang.

I have not idea what they are doing here, but the same construct is used
all over Frameworks/Kernel.framework/Headers.

> We do have control, IIRC, about adding the frameworks search path to "sys=
tem"
> rather than "user".

That might be an option: I guess we should follow what clang does here.=