Robert N. M. Watson

Tagging @bsdjhb @brooksdavis @arichardson @jrtc27.

I think my thoughts on this suggestion are a bit different: I don't think we want to define what the ABI is specifically in the CHERI C/C++ document, but that...

Yes, this sounds good. What immediately come to mind are memory allocation functions, such as `malloc()`, `realloc()`, and so on. Do you have other things in mind as well? It...

Experience this far suggests that consumers of interfaces such as `sort()`, `strpos()`, and `strtok()` sometimes expect the returned string pointer to continue to allow access to other bits of the...

I think it is safe to say that we have a pretty good understanding of bounds behaviour at the granularity of the allocation, but that experiments with sub-object bounds generally...

(But, to be clear, we've not reviewed POSIX (for example) for other opportunities in any detail. Perhaps there are cases where arrays are indexed and a pointer returned, and yet...

#10 created to address C-language definitions and their bounds/permissions, as distinct from standard library APIs.

I guess also this would include some guidance (not sure how strong on the 'may' 'should' 'most' spectrum) along the lines of return values when allocating zero-size regions, how to...

It might also be that we want to consider how to handle optional types of protection -- e.g., at least "No temporal safety" vs "With temporal safety" -- but the...

Tagging @brettferdosi, @brooksdavis