Author: tim.bunce
Date: Wed Oct 29 15:51:39 2008
New Revision: 576
Modified:
trunk/HACKING
trunk/MANIFEST
trunk/lib/Devel/NYTProf.pm
Log:
Update MANIFEST for new file in previous commit.
Add more docs aboit clock=N option.
Modified: trunk/HACKING
==============================================================================
--- trunk/HACKING (original)
+++ trunk/HACKING Wed Oct 29 15:51:39 2008
@@ -277,8 +277,6 @@
Slow builtins, eg those that make system calls or are otherwise expensive,
like crypt,
could be treated as calls to xsubs in the CORE:: namespace.
-Consider use of CLOCK_PROF for (higher-resolution?) cpu time measurement
-
Replace DB::enable_profiling() and DB::disable_profiling() with
$DB::profile = 1|0;
That a more consistent API with $DB::single etc., but more importantly it
lets
users leave the code in place when NYTProf is not loaded. It'll just do
nothing,
Modified: trunk/MANIFEST
==============================================================================
--- trunk/MANIFEST (original)
+++ trunk/MANIFEST Wed Oct 29 15:51:39 2008
@@ -101,4 +101,5 @@
t/test80-recurs.p
t/test80-recurs.rdt
typemap
+xt/test71-while.p
xt/test90-stress.p
Modified: trunk/lib/Devel/NYTProf.pm
==============================================================================
--- trunk/lib/Devel/NYTProf.pm (original)
+++ trunk/lib/Devel/NYTProf.pm Wed Oct 29 15:51:39 2008
@@ -20,7 +20,7 @@
# Set the flags that influence compilation ASAP so we get full details
# (sub line ranges etc) of modules loaded as a side effect of loading
# Devel::NYTProf::Core (ie XSLoader, strict, Exporter etc.)
-# See "perldoc perlvar" for details of the $^P flags
+# See "perldoc perlvar" for details of the $^P ($PERLDB) flags
$^P = 0x010 # record line range of sub definition
| 0x100 # informative "file" names for evals
| 0x200; # informative names for anonymous subroutines
@@ -28,8 +28,8 @@
# XXX hack, need better option handling
my $use_db_sub = ($ENV{NYTPROF} && $ENV{NYTPROF} =~ m/\buse_db_sub=1\b/);
-$^P |= 0x002 # line-by-line profiling (if $DB::single true)
- | 0x020 # start (after BEGINs) with single-step on
+$^P |= 0x002 # line-by-line profiling via DB::DB (if $DB::single true)
+ | 0x020 # start (after BEGINs) with single-step on
if $use_db_sub;
require Devel::NYTProf::Core; # loads XS
@@ -331,9 +331,15 @@
happen so rarely relative to the activity of a most applications that you'd
have to run the code for many hours to have any hope of reasonably useful
results.
-(It may be possible to use the C<clock=N> option to select a
-high-resolution cpu time clock. I've not tried that yet.
-If you try it, please let me know how it works out.)
+It may be possible to use the C<clock=N> option to select a
+high-resolution cpu time clock. You can find the clocks available
+on you system using a command like:
+
+ grep -r 'define *CLOCK_' /usr/include
+
+Look for a group that includes CLOCK_REALTIME. Documentation on these
clocks
+can be hard to find. I've not tried using these clocks yet. If you try it,
+please let us know how it works out.
=head2 file=...
--~--~---------~--~----~------------~-------~--~----~
You've received this message because you are subscribed to
the Devel::NYTProf Development User group.
Group hosted at: http://groups.google.com/group/develnytprof-dev
Project hosted at: http://perl-devel-nytprof.googlecode.com
CPAN distribution: http://search.cpan.org/dist/Devel-NYTProf
To post, email: [email protected]
To unsubscribe, email: [EMAIL PROTECTED]
-~----------~----~----~----~------~----~------~--~---
