public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <bug-114049-4-4VTC5fHIQr@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114049-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #4 from ro at CeBiTec dot Uni-Bielefeld.DE <ro at CeBiTec dot Uni-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 "system"
> rather than "user".

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

  parent reply	other threads:[~2024-02-22 13:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-22  9:56 [Bug target/114049] New: " ro at gcc dot gnu.org
2024-02-22  9:57 ` [Bug target/114049] " ro at gcc dot gnu.org
2024-02-22 10:40 ` iains at gcc dot gnu.org
2024-02-22 12:06 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-02-22 13:14 ` iains at gcc dot gnu.org
2024-02-22 13:28 ` ro at CeBiTec dot Uni-Bielefeld.DE [this message]
2024-02-22 13:55 ` iains at gcc dot gnu.org
2024-02-23 11:03 ` iains at gcc dot gnu.org
2024-03-07 16:52 ` fxcoudert at gcc dot gnu.org
2024-03-16 15:51 ` iains at gcc dot gnu.org
2024-03-19 13:00 ` cvs-commit at gcc dot gnu.org
2024-03-19 16:02 ` iains at gcc dot gnu.org
2024-04-04 18:36 ` cvs-commit at gcc dot gnu.org
2024-04-21 13:03 ` cvs-commit at gcc dot gnu.org
2024-04-29 14:18 ` cvs-commit at gcc dot gnu.org
2024-04-29 14:41 ` iains at gcc dot gnu.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-114049-4-4VTC5fHIQr@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).