From: "Jₑₙₛ Gustedt" <jens.gustedt@inria.fr>
To: Rich Felker <dalias@libc.org>
Cc: musl@lists.openwall.com
Subject: Re: [musl] [C23 new stdlib 2/4] C23: add the memalignment function
Date: Thu, 25 May 2023 16:05:01 +0200 [thread overview]
Message-ID: <20230525160501.787872b2@inria.fr> (raw)
In-Reply-To: <20230525130723.GH4163@brightrain.aerifal.cx>
[-- Attachment #1: Type: text/plain, Size: 2154 bytes --]
on Thu, 25 May 2023 09:07:23 -0400 you (Rich Felker <dalias@libc.org>)
wrote:
> > So you want me to use the ctz and clz interfaces from the internal
> > atomics for the implementation of <stdbit.h>? Are they not overkill
> > for this simple purpose? (I mean they are meant to be atomic,
> > arent't they?)
>
> No, I think you're mixing up code which is part of musl and code which
> is (included as) part of the application. atomic.h is a musl
> implementation detail and is not even present for application code
> included from stdbit.h to use.
I am not clear to which question you are answering "no". Fact is that
these functions are used for `ffs` and friends, so they are the
natural candidates to base the implementation upon. (`ffs` cannot be
used directly because they have intefaces with signed integers.)
I'd very much like to avoid to reinvent the wheel, here, and in the
internal code that I have looked at I have not detected much which
would be specific for atomics. But maybe I am overlooking something,
thus the question.
> See NRK's follow-up. If pure header-only implementations of these
> interfaces met the requirements of the standard, I could see a good
> argument for having implementations there. But if they require
> external functions, I'm not clear on why it makes sense to implement
> inline versions in the headers rather than just letting the compiler
> do its own transformations to inline if/when it wants. This was a path
> glibc went down a long time ago with "bits/string2.h", putting gobs of
> attempted-optimized code in public headers that was suppressing gcc's
> builtin, much better optimizations for the same functions via its
> __builtin_*. I don't think we should repeat that.
Yes, thanks, I understand that strategy much better now.
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-25 14:05 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 19:38 [musl] [C23 new stdlib 0/4] changes in stdlib.h Jens Gustedt
2023-05-24 19:38 ` [musl] [C23 new stdlib 1/4] C23: add the new interfaces free_sized and free_aligned_sized for stdlib.h Jens Gustedt
2023-05-24 21:31 ` Rich Felker
2023-05-25 9:38 ` Jₑₙₛ Gustedt
2023-05-25 12:57 ` Rich Felker
2023-05-24 19:38 ` [musl] [C23 new stdlib 2/4] C23: add the memalignment function Jens Gustedt
2023-05-24 21:28 ` Rich Felker
2023-05-24 22:12 ` Rich Felker
2023-05-25 9:17 ` Jₑₙₛ Gustedt
2023-05-25 9:16 ` Jₑₙₛ Gustedt
2023-05-25 9:42 ` NRK
2023-05-25 13:07 ` Rich Felker
2023-05-25 14:05 ` Jₑₙₛ Gustedt [this message]
2023-05-25 14:34 ` Rich Felker
2023-05-25 15:22 ` Jₑₙₛ Gustedt
2023-06-01 13:35 ` Alexander Monakov
2023-06-01 19:08 ` Rich Felker
2023-06-02 8:07 ` Jₑₙₛ Gustedt
2023-06-02 8:03 ` Jₑₙₛ Gustedt
2023-06-02 8:37 ` Alexander Monakov
2023-05-24 19:38 ` [musl] [C23 new stdlib 3/4] C23: implement the new strfrom[dfl] functions Jens Gustedt
2023-05-24 21:42 ` Rich Felker
2023-05-24 19:38 ` [musl] [C23 new stdlib 4/4] C23: add the new include guard to stdlib.h Jens 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=20230525160501.787872b2@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).