Re: *alloc: Take advantage of CHERI bounds-checking

[Paul Eggert]

On 2023-11-12 19:10, Bruno Haible wrote:
> So, if I understood it correctly, in hybrid mode (2), programs (especially
> memory allocators)_can_  use <cheri.h> and its functions, but it's not
> necessary since the programs will also work without it?

So __CHERI__ currently means "either hybrid or pure capability mode" and 
__CHERI_PURE_CAPABILITY__ means "pure capability mode only"? And the 
CHERI folks are thinking of changing __CHERI__ so that it will mean 
"pure capability mode only" in some future version?

It sounds like we should not use __CHERI__, since (a) it doesn't 
currently mean what we think it means and (b) it's not portable to the 
future. And we should change all instances of __CHERI__ to 
__CHERI_PURE_CAPABILITY__, hoping that __CHERI_PURE_CAPABILITY__ will 
continue to mean what it does now.