Change the push/unshift warning to be of class syntax, not misc.

[p5sagit/p5-mst-13.2.git] / pod / perlhack.pod

diff --git a/pod/perlhack.pod b/pod/perlhack.pod
index a5fbc20..cec4281 100644 (file)
--- a/pod/perlhack.pod
+++ b/pod/perlhack.pod
@@ -410,7 +410,7 @@ the current source tree (i.e. perl@7582.tar.gz), which will be an
 excellent point to start with when choosing to use the 'rsync the
 patches' scheme. Starting with perl@7582, which means a set of source
 files on which the latest applied patch is number 7582, you apply all
-succeeding patches available from than on (7583, 7584, ...).
+succeeding patches available from then on (7583, 7584, ...).
 
 You can use the patches later as a kind of search archive.
 
@@ -486,7 +486,7 @@ Your patch should update the documentation and test suite.
 
 To report a bug in Perl, use the program I<perlbug> which comes with
 Perl (if you can't get Perl to work, send mail to the address
-I<perlbug@perl.com> or I<perlbug@perl.org>).  Reporting bugs through
+I<perlbug@perl.org> or I<perlbug@perl.com>).  Reporting bugs through
 I<perlbug> feeds into the automated bug-tracking system, access to
 which is provided through the web at I<http://bugs.perl.org/>.  It
 often pays to check the archives of the perl5-porters mailing list to
@@ -1730,25 +1730,75 @@ need to do too, if you don't want to see the "global leaks":
 
 =head2 Pixie Profiling
 
-Pixie is a profiling tool available on Tru64 (aka Digital UNIX aka DEC
-OSF/1) and IRIX platforms.  Pixie does its profiling using
-"basic-block counting".  A basic block is a program region that
+Pixie is a profiling tool available on IRIX and Tru64
+(aka Digital UNIX aka DEC OSF/1) platforms.  Pixie does its profiling
+using "basic-block counting".  A basic block is a program region that
 is entered only at the beginning and exited only at the end.
 
 You can build a profiled version of perl called "perl.pixie" by
 invoking the make target "perl.pixie" (in Tru64 a file called
 "perl.Addrs" will also be silently created, this file contains the
 addresses of the basic blocks).  Running the profiled version of Perl
-will create a new file called "Perl.Counts" which contains the basic
-block counts for that particular run.
+will create a new file called "perl.Counts" which contains the counts
+for the basic block for that particular program execution.
 
 To display the results you must use the "prof" utility.  The exact
 incantation depends on your operating system, "prof perl.Counts" in
 IRIX, and "prof -pixie -all -L. perl" in Tru64.
 
-By default prof shows the most executed source code lines in
-descending order of use.  For further information, see your system's
-manual pages for pixie and prof.
+In IRIX the following prof options are available:
+
+=over 4
+
+=item -h
+
+Reports the most heavily used lines in descending order of use.
+Useful for finding the hotspot lines.
+
+=item -l
+
+Groups lines by procedure, with procedures sorted in descending order of use.
+Within a procedure, lines are listed in source order.
+Useful for finding the hotspots of procedures.
+
+=back
+
+In Tru64 the following options are available:
+
+=over 4
+
+=item -p
+
+Procecures sorted in descending order by the number of cycles executed
+in each procedure.  Useful for finding the hotspot procedures.
+(This is the default option.)
+
+=item -h
+
+Lines sorted in descending order by the number of cycles executed in
+each line.  Useful for finding the hotspot lines.
+
+=item -i
+
+The called procedures are sorted in descending order by number of calls
+made to the procedures.  Useful for finding the most used procedures.
+
+=item -l
+
+Grouped by procedure, sorted by cycles executed per procedure.
+Useful for finding the hotspots of procedures.
+
+=item -testcoverage
+
+The compiler emitted code for these lines, but the code was unexecuted.
+
+=item -zero
+
+Unexecuted procedures.
+
+=back
+
+For further information, see your system's manual pages for pixie and prof.
 
 =head2 CONCLUSION