nikic wrote: > @nikic By the way, are there plans to support allocation functions other than > alloca in this check? I don't see currently any llvm passes assigning > dereferenceable(_or_null) attribute to something like `malloc(42)` , but I > don't see why not and in that case this should also be something not reliant > on the context.
I believe we don't mark allocation return values as dereferencable because it would imply a too strong property right now (staying dereferenceable even after the allocation was freed). https://github.com/llvm/llvm-project/pull/109277 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
