From: "Jₑₙₛ Gustedt" <jens.gustedt@inria.fr>
To: enh <enh@google.com>
Cc: musl@lists.openwall.com,
"罗勇刚(Yonggang Luo)" <luoyonggang@gmail.com>,
"Jason Ekstrand" <jason@jlekstrand.net>
Subject: Re: [musl] C23 implications for C libraries
Date: Thu, 4 May 2023 08:19:42 +0200 [thread overview]
Message-ID: <20230504081942.065fc12f@inria.fr> (raw)
In-Reply-To: <CAJgzZoqcdv8XfP2aNNq5ziqY=tWXZD0KWQvSLrf-mnwFwZ9Cxw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1406 bytes --]
Hi,
on Wed, 3 May 2023 15:58:26 -0700 you (enh <enh@google.com>) wrote:
> (i share others' skepticism that timespec_get() is very useful,
I don't think that these interfaces by themselves are the most
interesting. The original motivation to create these interfaces stem
from the creation the integration of threads in to the C standard. And
there the monotonic and thread-specific clocks make all their sense.
But also having process cpu usage in a well-defined interface (`clock`
usage is not portable for that) is a win.
> and especially that non-ISO bases will ever be useful to anyway, but
> i like the idea of allowing future additions to "just work" with an
> old libc enough that i've implemented bionic's
> timespec_get()/timespec_getres() in this style.)
Great!
Do you have a link to that? The particular choices of values become
part of the ABI, sort-of. So it would be better to be consistent
between implementations.
Would this motivate musl to accept patches for the optional bases that
come with C23? Or maybe the whole set?
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 --]
next prev parent reply other threads:[~2023-05-04 6:20 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-23 14:25 Jₑₙₛ Gustedt
2022-09-23 14:58 ` Rich Felker
2022-09-23 15:11 ` Alexander Monakov
2022-09-23 15:35 ` Jₑₙₛ Gustedt
2022-09-23 15:28 ` enh
2022-09-23 15:40 ` Jₑₙₛ Gustedt
2022-09-23 23:52 ` enh
2022-09-24 7:31 ` Jₑₙₛ Gustedt
2022-09-26 3:18 ` Damian McGuckin
2022-09-26 3:33 ` Rich Felker
2022-09-26 10:49 ` Florian Weimer
2022-09-26 12:52 ` Jₑₙₛ Gustedt
2022-09-26 20:13 ` enh
2022-11-18 20:46 ` 罗勇刚(Yonggang Luo)
2022-11-19 14:33 ` Jₑₙₛ Gustedt
2022-11-19 17:19 ` 罗勇刚(Yonggang Luo)
2022-11-20 8:23 ` Jₑₙₛ Gustedt
2022-11-19 18:28 ` Rich Felker
2022-11-20 8:42 ` Jₑₙₛ Gustedt
2023-05-03 22:58 ` enh
2023-05-04 6:19 ` Jₑₙₛ Gustedt [this message]
2023-05-04 16:03 ` Rich Felker
2023-05-04 16:07 ` enh
2023-05-04 23:16 ` Gabriel Ravier
2023-05-05 0:37 ` JeanHeyd Meneide
2023-05-05 6:56 ` Jₑₙₛ Gustedt
2023-05-05 12:40 ` Rich Felker
2023-05-05 6:40 ` Jₑₙₛ Gustedt
2023-05-04 16:03 ` enh
2023-05-04 23:11 ` Gabriel Ravier
2022-11-19 18:31 ` Rich Felker
2022-11-20 4:25 ` 罗勇刚(Yonggang Luo)
2022-11-20 5:34 ` Markus Wichmann
2022-11-21 11:46 ` Reini Urban
2022-11-21 21:06 ` Jₑₙₛ Gustedt
2022-11-23 4:31 ` 罗勇刚(Yonggang Luo)
2022-11-23 8:11 ` Jₑₙₛ Gustedt
2022-11-23 8:20 ` 罗勇刚(Yonggang Luo)
2022-11-23 8:33 ` Jₑₙₛ Gustedt
2022-11-23 8:41 ` 罗勇刚(Yonggang Luo)
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=20230504081942.065fc12f@inria.fr \
--to=jens.gustedt@inria.fr \
--cc=enh@google.com \
--cc=jason@jlekstrand.net \
--cc=luoyonggang@gmail.com \
--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).