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.

diff --git a/ChangeLog b/ChangeLog
index 2e13d668a76f9c89f3874a610baf914d3bfbaeae..ad8e78ef7b8a64b7a2f7060fc6e0e8e99ed8d07c 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -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

diff --git a/malloc/malloc.c b/malloc/malloc.c
index 068ffc1684cc368bbeceb95d6d310b6042311e1c..aa45626093b806fcb27be5698a986c8feeb7f2bb 100644 (file)
--- a/malloc/malloc.c
+++ b/malloc/malloc.c
@@ -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.