[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 31 May 2023 16:42:54 +0200
From: Jₑₙₛ Gustedt <jens.gustedt@...ia.fr>
To: Rich Felker <dalias@...c.org>
Cc: musl@...ts.openwall.com
Subject: Re: [C23 128 bit 4/4] C23: implement proper support for
int128_t and uint128_t
Rich,
on Wed, 31 May 2023 10:27:44 -0400 you (Rich Felker <dalias@...c.org>)
wrote:
> (This was the whole reason _BitInt was added, no?)
No, not at all. These are added to have
- types for any width, not only multiples of 8
- potentially have types that have thousands of bits (clang seems to
be keen to do so)
- types that have different rules for conversions, in particular no promotion.
These are explicitly not allowed to be used for the [u]intXXX_t types.
They only appear in the patches I propose as a means to encode number
literals of the appropriate width. These are used with casts, such
that they end up with the correct types.
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 ::
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
