5a298e8685
This change introduce 2 items: 1. If the size of the space requested is 0, the behavior is implementation-defined: either a null pointer shall be returned, or the behavior shall be as if the size were some non-zero value, except that the behavior is undefined if the returned pointer is used to access an object. Change the behavior to be similar to Linux and Android and allocates an object of a minimum size instead of returning null pointer. https://pubs.opengroup.org/onlinepubs/9699919799/functions/malloc.html https://pubs.opengroup.org/onlinepubs/9699919799/functions/calloc.html https://pubs.opengroup.org/onlinepubs/9699919799/functions/realloc.html 2. The description of realloc() has been modified from previous versions of this standard to align with the ISO/IEC 9899:1999 standard. Previous versions explicitly permitted a call to realloc (p, 0) to free the space pointed to by p and return a null pointer. While this behavior could be interpreted as permitted by this version of the standard, the C language committee have indicated that this interpretation is incorrect. Applications should assume that if realloc() returns a null pointer, the space pointed to by p has not been freed. Since this could lead to double-frees, implementations should also set errno if a null pointer actually indicates a failure, and applications should only free the space if errno was changed. Do not free memory of zero-length reallocation is requested https://pubs.opengroup.org/onlinepubs/9699919799/functions/realloc.html Co-authored-by: fangxinyong <fangxinyong@xiaomi.com> Signed-off-by: Petro Karashchenko <petro.karashchenko@gmail.com> |
||
---|---|---|
.. | ||
Make.defs | ||
umm_addregion.c | ||
umm_brkaddr.c | ||
umm_calloc.c | ||
umm_checkcorruption.c | ||
umm_extend.c | ||
umm_free.c | ||
umm_globals.c | ||
umm_heap.h | ||
umm_heapmember.c | ||
umm_initialize.c | ||
umm_mallinfo.c | ||
umm_malloc.c | ||
umm_malloc_size.c | ||
umm_memalign.c | ||
umm_memdump.c | ||
umm_realloc.c | ||
umm_sbrk.c | ||
umm_zalloc.c |