ColinKinloch wrote:

One of the diagnostics I'm in the process of porting is to check the `count` 
argument of `read`, `pwrite`, etc. against `SSIZE_MAX` to validate that the 
size requested operation doesn't exceed the platforms maximum operation size.

Alongside a lookup for platform specific values (max signed long on darwin, 
signed size type on glibc) I'm trying to infer the value of `SSIZE_MAX` by 
checking the size of the return type of the function (ssize_t). However if I've 
set it as a builtin will that always be the same? And would the builtin 
function necessarily match the platforms signature?

https://github.com/llvm/llvm-project/pull/161737
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits

Reply via email to