Displaying 1 result from an estimated 1 matches for "my_useless_buff".
Did you mean:
my_useless_buffer
2015 Apr 01
3
[LLVMdev] why we assume malloc() always returns a non-null pointer in instruction combing?
Hi David and Mats,
Thanks for your explanation. If my understanding is correct, it means we
don't need to consider the side-effect of malloc/free unless compiling with
-ffreestanding. Because without -ffreestanding, user defined malloc/free
should be compatible with std library. It makes sense to me.
My point is, in std library, malloc is allowed to return null if this
malloc failed. Why