Paul Eggert wrote:
> > Which integer types on CHERI have "holes"?
>
> intptr_t and uintptr_t, since they consume 128 bits of storage but have
> only 64 bits of integer value payload.
Oh, indeed. I had through that intptr_t and uintptr_t support normal 128-bit
integer arithmetic, but this is not
On 2023-12-01 22:12, Bruno Haible wrote:
Which integer types on CHERI have "holes"?
intptr_t and uintptr_t, since they consume 128 bits of storage but have
only 64 bits of integer value payload. Because of the holes, for
example, intprops.h's TYPE_MAXIMUM doesn't work on CHERI-BSD for those
Paul Eggert wrote:
> * doc/gnulib-readme.texi:
> Prefer “null pointer” to “@code{NULL}” since C23 has nullptr.
> (Portability guidelines): Mention C99 instead of C89 for what
> Gnulib assumes of headers.
> (C99 features avoided): Mention CHERI issue with intptr_t etc.
> (Other portability assumptio
* doc/gnulib-readme.texi:
Prefer “null pointer” to “@code{NULL}” since C23 has nullptr.
(Portability guidelines): Mention C99 instead of C89 for what
Gnulib assumes of headers.
(C99 features avoided): Mention CHERI issue with intptr_t etc.
(Other portability assumptions): Say that C23 requires two’
