[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230531145724.GF4163@brightrain.aerifal.cx>
Date: Wed, 31 May 2023 10:57:24 -0400
From: Rich Felker <dalias@...c.org>
To: Jₑₙₛ Gustedt <jens.gustedt@...ia.fr>
Cc: musl@...ts.openwall.com
Subject: Re: [C23 128 bit 4/4] C23: implement proper support for
int128_t and uint128_t
On Wed, May 31, 2023 at 04:55:45PM +0200, Jₑₙₛ Gustedt wrote:
> Rich,
>
> on Wed, 31 May 2023 10:41:29 -0400 you (Rich Felker <dalias@...c.org>)
> wrote:
>
> > On Wed, May 31, 2023 at 04:36:43PM +0200, Jₑₙₛ Gustedt wrote:
> > > Rich,
> > >
> > > on Wed, 31 May 2023 10:27:44 -0400 you (Rich Felker
> > > <dalias@...c.org>) wrote:
> > >
> > > > Unless the rules in C23 changed,
> > >
> > > They did change, this is what this is all about.
> >
> > Can you cite that?
>
> sure, almost by heart, since I wrote that ;-)
>
> … with the possible exceptions of signed bit-precise integer types
> and of signed extended integer types that are wider than `long long`
> and that are referred by the type definition for an exact width
> integer type
>
> > Because I don't see it. I still see that intmax_t
> > has to be at least as wide as all the intN_t.
>
> I seems that you read that the wrong way around.
OK, so AIUI based on this exception it's permitted but not required to
offer int128_t.
Rich
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.
