From: Rich Felker <dalias@libc.org>
To: "Jₑₙₛ Gustedt" <jens.gustedt@inria.fr>
Cc: musl@lists.openwall.com
Subject: Re: [musl] patches for C23
Date: Wed, 3 May 2023 10:43:46 -0400 [thread overview]
Message-ID: <20230503144346.GX4163@brightrain.aerifal.cx> (raw)
In-Reply-To: <20230503162649.19e2e95b@inria.fr>
On Wed, May 03, 2023 at 04:26:49PM +0200, Jₑₙₛ Gustedt wrote:
> Rich,
>
> on Wed, 3 May 2023 10:06:20 -0400 you (Rich Felker <dalias@libc.org>)
> wrote:
>
> > I'd rather just fix it in one place (the implementation-internal
> > header) so we don't have to worry about it.
>
> I still don't understand which header that is supposed to be.
See src/include/*.h. These headers so far mostly just declare
additional __-prefixed versions of interfaces where needed, but some
of them do additional things. For example, src/include/stdio.h does
some additional things:
- suppresses the complete definition of FILE, which conflicts with
libc-internal use where we have a real structure not a gratuitous
fake type for pre-c11 (and POSIX) conformance reasons.
- replaces the stdin/out/err macros with ones that resolve directly to
address-of the internal objects rather than pointer objects subject
to copy relocations -- this makes internal codegen a lot more
efficient for functions which implicitly use stdin/out.
Some other things I eventually intend to do in src/include/*:
- making memcpy expand to __builtin_memcpy if available, and similar
for other string functions with builtins; the few places where that
could be problem would need to #undef them.
- making calls to some functions where the interposable call overhead
is likely significant expand to direct calls to hidden aliases.
- etc.
Undefining macro definitions that are unsuitable for some reason to
the implementation-internal code in libc is another perfectly good use
for these.
Rich
next prev parent reply other threads:[~2023-05-03 14:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-01 18:50 Jₑₙₛ Gustedt
2023-05-01 19:24 ` Khem Raj
2023-05-01 19:41 ` Rich Felker
2023-05-02 6:57 ` Jₑₙₛ Gustedt
2023-05-02 13:59 ` Jₑₙₛ Gustedt
2023-05-02 23:20 ` Rich Felker
2023-05-03 0:00 ` Rich Felker
2023-05-03 9:12 ` Jₑₙₛ Gustedt
2023-05-03 14:16 ` Rich Felker
2023-05-03 15:11 ` Jₑₙₛ Gustedt
2023-05-03 17:28 ` Rich Felker
2023-05-03 18:46 ` Jₑₙₛ Gustedt
2023-05-03 19:33 ` Rich Felker
2023-05-04 1:09 ` Gabriel Ravier
2023-05-04 14:07 ` Rich Felker
2023-05-04 6:48 ` Jₑₙₛ Gustedt
2023-05-04 14:30 ` Rich Felker
2023-05-04 15:31 ` enh
2023-05-04 15:53 ` Jₑₙₛ Gustedt
2023-05-04 16:14 ` Rich Felker
2023-05-10 14:17 ` Jₑₙₛ Gustedt
2023-05-10 14:28 ` [musl] stdbit.h Jₑₙₛ Gustedt
2023-05-04 15:50 ` [musl] patches for C23 Jeffrey Walton
2023-05-04 16:05 ` Rich Felker
2023-05-03 7:13 ` Jₑₙₛ Gustedt
2023-05-03 14:06 ` Rich Felker
2023-05-03 14:26 ` Jₑₙₛ Gustedt
2023-05-03 14:43 ` Rich Felker [this message]
2023-05-03 15:26 ` Jₑₙₛ Gustedt
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=20230503144346.GX4163@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=jens.gustedt@inria.fr \
--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).