summaryrefslogtreecommitdiff
path: root/README.tru64
diff options
context:
space:
mode:
authorJarkko Hietaniemi <jhi@iki.fi>2001-06-02 16:48:26 +0000
committerJarkko Hietaniemi <jhi@iki.fi>2001-06-02 16:48:26 +0000
commit8fa7f3676ed75809365905727fbae97dc8767f29 (patch)
tree2c626750a9a8493a188833eb82d96b24e79fa03f /README.tru64
parenta126002e7fdcd66f0996dbe9b5b1c2d7960cf31b (diff)
downloadperl-8fa7f3676ed75809365905727fbae97dc8767f29.tar.gz
-Wall cleanup continues.
p4raw-id: //depot/perl@10392
Diffstat (limited to 'README.tru64')
-rw-r--r--README.tru6412
1 files changed, 7 insertions, 5 deletions
diff --git a/README.tru64 b/README.tru64
index c551a36594..4eb6a001f9 100644
--- a/README.tru64
+++ b/README.tru64
@@ -15,11 +15,13 @@ is compiled and/or runs.
=head2 Compiling Perl 5 on Tru64
The recommended compiler to use in Tru64 is the native C compiler.
-The native compiler produces much faster code (the speed difference is
-noticeable: several dozen percentages) and also more correct code: if you
-are considering using the GNU C compiler you should use the gcc 2.95.3
-release since older gcc releases are known to produce buggy code when
-compiling Perl.
+The native compiler produces much faster code (the speed difference
+is noticeable: several dozen percentages) and also more correct code:
+if you are considering using the GNU C compiler you should use the
+gcc 2.95.3 since all older gcc releases are known to produce broken
+code when compiling Perl. One manifestation of this brokenness is
+the lib/sdbm test dumping core; another is the op/regexp dumping core
+(depending on the GCC release).
=head2 Using Large Files with Perl on Tru64