Tweak realloc/MREMAP comment to be more accurate.

MMap'd memory isn't shrunk without MREMAP, but IIRC this is intentional for
performance reasons.  Regardless, this patch tweaks the existing comment to
be more accurate wrt the existing code.

	[BZ #21411]
	* malloc/malloc.c: Tweak realloc/MREMAP comment to be more accurate.
This commit is contained in:
DJ Delorie 2017-05-03 16:25:15 -04:00
parent e35ac97cc8
commit 3b5f801ddb
2 changed files with 8 additions and 3 deletions

View File

@ -1,3 +1,8 @@
2017-05-03 DJ Delorie <dj@redhat.com>
[BZ #21411]
* malloc/malloc.c: Tweak realloc/MREMAP comment to be more accurate.
2017-05-03 Phil Blundell <pb@pbcl.net>
* inet/netinet/in.h (struct ip_mreq_source): Correct misplaced

View File

@ -514,9 +514,9 @@ void* __libc_calloc(size_t, size_t);
REALLOC_ZERO_BYTES_FREES is set, realloc with a size argument of
zero (re)allocates a minimum-sized chunk.
Large chunks that were internally obtained via mmap will always
be reallocated using malloc-copy-free sequences unless
the system supports MREMAP (currently only linux).
Large chunks that were internally obtained via mmap will always be
grown using malloc-copy-free sequences unless the system supports
MREMAP (currently only linux).
The old unix realloc convention of allowing the last-free'd chunk
to be used as an argument to realloc is not supported.