From: "Jₑₙₛ Gustedt" <jens.gustedt@inria.fr>
To: Rich Felker <dalias@libc.org>
Cc: musl@lists.openwall.com
Subject: Re: [musl] [C23 implied 2/2] clang: only exclude C library includes, but allow compiler specific headers
Date: Wed, 24 May 2023 15:39:09 +0200 [thread overview]
Message-ID: <20230524153909.2a270e58@inria.fr> (raw)
In-Reply-To: <20230524133233.GT4163@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 819 bytes --]
Rich,
on Wed, 24 May 2023 09:32:33 -0400 you (Rich Felker <dalias@libc.org>)
wrote:
> It's not clear to me whether this works on all versions, but more
> importantly, it's not clear whether it blocks the compiler header path
> from being searched before the libc header path, which is necessary so
> incompatible compiler-provided stdc headers don't get used.
That's the idea, yes. I am building this systematically for clang
versions 9 to 17, and it seems all work fine.
Thanks
Jₑₙₛ
--
:: ICube :::::::::::::::::::::::::::::: deputy director ::
:: Université de Strasbourg :::::::::::::::::::::: ICPS ::
:: INRIA Nancy Grand Est :::::::::::::::::::::::: Camus ::
:: :::::::::::::::::::::::::::::::::::: ☎ +33 368854536 ::
:: https://icube-icps.unistra.fr/index.php/Jens_Gustedt ::
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2023-05-24 13:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 10:03 [musl] [C23 implied 0/2] stuff detected with the intended changes Jens Gustedt
2023-04-16 20:41 ` [musl] [C23 implied 1/2] C23: update some legacy function pointers Jens Gustedt
2023-04-17 19:30 ` [musl] [C23 implied 2/2] clang: only exclude C library includes, but allow compiler specific headers Jens Gustedt
2023-05-24 13:32 ` Rich Felker
2023-05-24 13:39 ` Jₑₙₛ Gustedt [this message]
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=20230524153909.2a270e58@inria.fr \
--to=jens.gustedt@inria.fr \
--cc=dalias@libc.org \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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 NNTP newsgroup(s).