MAking Solaris malloc() the default

Message-ID: <20010129125936.Z4830@alanya.lupe-christoph.de>

The README.solaris part slightly tweaked.

p4raw-id: //depot/perl@8588

1 files changed, 10 insertions, 17 deletions

diff --git a/README.solaris b/README.solaris
index 97e84a3622..1a36a8a94a 100644
--- a/README.solaris
+++ b/README.solaris
@@ -358,13 +358,6 @@ instead.
 All this should be handled automatically by the hints file, if
 requested.
 
-If you do want to be able to allocate more than 4GB memory inside
-perl, then you should use the Solaris malloc, since the perl
-malloc breaks when dealing with more than 2GB of memory.  You can do
-this with
-
-	sh Configure -Uusemymalloc
-
 =head3 Long Doubles.
 
 As of 5.6.0, long doubles are not working.
@@ -379,22 +372,22 @@ in -lrt.  The hints file should handle adding this automatically.
 
 =head2 Malloc Issues.
 
+Starting from Perl 5.7.1 Perl uses the Solaris malloc, since the perl
+malloc breaks when dealing with more than 2GB of memory, and the Solaris
+malloc also seems to be faster.
+
+If you for some reason (such as binary backward compatibility) really
+need to use perl's malloc, you can rebuild Perl from the sources
+and Configure the build with 
+
+	sh Configure -Dusemymalloc
+  
 You should not use perl's malloc if you are building with gcc.  There
 are reports of core dumps, especially in the PDL module.  The problem
 appears to go away under -DDEBUGGING, so it has been difficult to
 track down.  Sun's compiler appears to be ok with or without perl's
 malloc. [XXX further investigation is needed here.]
 
-You should also not use perl's malloc if you are building perl as
-an LP64 application, since perl's malloc has trouble allocating more
-than 2GB of memory.
-
-You can avoid perl's malloc by Configuring with
-
-	sh Configure -Uusemymalloc
-
-[XXX Update hints file.]
-
 =head1 MAKE PROBLEMS.
 
 =over 4