.\" Automatically generated by Pod::Man v1.34, Pod::Parser v1.13
.\" ========================================================================
.de Sh \" Subsection heading
.de Sp \" Vertical space (when we can't use .PP)
.de Vb \" Begin verbatim text
.de Ve \" End verbatim text
.\" Set up some character translations and predefined strings. \*(-- will
.\" give an unbreakable dash, \*(PI will give pi, \*(L" will give a left
.\" double quote, and \*(R" will give a right double quote. | will give a
.\" real vertical bar. \*(C+ will give a nicer C++. Capital omega is used to
.\" do unbreakable dashes and therefore won't be available. \*(C` and \*(C'
.\" expand to `' in nroff, nothing in troff, for use with C<>.
.ds C+ C\v'-.1v'\h'-1p'\s-2+\h'-1p'+\s0\v'.1v'\h'-1p'
. if (\n(.H=4u)&(1m=24u) .ds -- \(*W\h'-12u'\(*W\h'-12u'-\" diablo 10 pitch
. if (\n(.H=4u)&(1m=20u) .ds -- \(*W\h'-12u'\(*W\h'-8u'-\" diablo 12 pitch
.\" If the F register is turned on, we'll generate index entries on stderr for
.\" titles (.TH), headers (.SH), subsections (.Sh), items (.Ip), and index
.\" entries marked with X<> in POD. Of course, you'll have to process the
.\" output yourself in some meaningful fashion.
. tm Index:\\$1\t\\n%\t"\\$2"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
.\" Fear. Run. Save yourself. No user-serviceable parts.
. \" fudge factors for nroff and troff
. ds #H ((1u-(\\\\n(.fu%2u))*.13m)
. \" simple accents for nroff and troff
. ds ' \\k:\h'-(\\n(.wu*8/10-\*(#H)'\'\h"|\\n:u"
. ds ` \\k:\h'-(\\n(.wu*8/10-\*(#H)'\`\h'|\\n:u'
. ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'^\h'|\\n:u'
. ds , \\k:\h'-(\\n(.wu*8/10)',\h'|\\n:u'
. ds ~ \\k:\h'-(\\n(.wu-\*(#H-.1m)'~\h'|\\n:u'
. ds / \\k:\h'-(\\n(.wu*8/10-\*(#H)'\z\(sl\h'|\\n:u'
. \" troff and (daisy-wheel) nroff accents
.ds : \\k:\h'-(\\n(.wu*8/10-\*(#H+.1m+\*(#F)'\v'-\*(#V'\z.\h'.2m+\*(#F'.\h'|\\n:u'\v'\*(#V'
.ds 8 \h'\*(#H'\(*b\h'-\*(#H'
.ds o \\k:\h'-(\\n(.wu+\w'\(de'u-\*(#H)/2u'\v'-.3n'\*(#[\z\(de\v'.3n'\h'|\\n:u'\*(#]
.ds d- \h'\*(#H'\(pd\h'-\w'~'u'\v'-.25m'\f2\(hy\fP\v'.25m'\h'-\*(#H'
.ds D- D\\k:\h'-\w'D'u'\v'-.11m'\z\(hy\v'.11m'\h'|\\n:u'
.ds th \*(#[\v'.3m'\s+1I\s-1\v'-.3m'\h'-(\w'I'u*2/3)'\s-1o\s+1\*(#]
.ds Th \*(#[\s+2I\s-2\h'-\w'I'u*3/5'\v'-.3m'o\v'.3m'\*(#]
.ds ae a\h'-(\w'a'u*4/10)'e
.ds Ae A\h'-(\w'A'u*4/10)'E
. \" corrections for vroff
.if v .ds ~ \\k:\h'-(\\n(.wu*9/10-\*(#H)'\s-2\u~\d\s+2\h'|\\n:u'
.if v .ds ^ \\k:\h'-(\\n(.wu*10/11-\*(#H)'\v'-.4m'^\v'.4m'\h'|\\n:u'
. \" for low resolution devices (crt and lpr)
.if \n(.H>23 .if \n(.V>19 \
.\" ========================================================================
.IX Title "AnalyzeDiag 3"
.TH AnalyzeDiag 3 "2004-05-07" "perl v5.8.0" "User Contributed Perl Documentation"
AnalyzeDiag \- Perl module for analyzing diag log files
\& my $analyzer = AnalyzeDiag::Analyzer->new(dir => $dir);
\& $analyzer->add_measurements
\& AnalyzeDiag::Measurement->new(name => 'PointerChase',
\& start => 'chase_start',
\& my %results = $analyzer->analyze();
\& my @times = @{ $Results{PointerChase} };
\& # Do something with times
\& This module exports some functions that analyze diag log
\& files. It is intended to be used by diags that write
\& their own post-processing scripts.
The AnalyzeDiag module contains two user-accessible classes:
AnalyzeDiag::Analyzer and AnalyzeDiag::Measurement.
The general usage is to create an AnalyzeDiag::Analyzer diag, given a
directory argument (see the example in the previous section). You
then add AnalyzeDiag::Measurement objects to the analyzer. Finally,
the call to the analyze method will produce a hash where the keys are
names of measurements and the values are arrays of times (in cycles)
The AnalyzeDiag::Measurement object has a contructor called 'new'.
Its argument is a hash with keys 'name', 'start', and 'end'. The name
field is used to identify the measurement. The 'start' and 'end'
values define PCs at which the measurement should start and end. They
may be virtual addresses (hex numbers without 0x) or labels.
.IP "verbose( [$level] )" 4
.IX Item "verbose( [$level] )"
If \f(CW$level\fR is specified, set verbose level to that. Returns verbosity
.IX Item "script_say(@msg)"
Print the message always.
Print the message if verbose level >= 1.
Print the message if verbose level >= 2.
.IP "script_warning(@msg)" 4
.IX Item "script_warning(@msg)"
.IX Item "script_die(@msg)"
Print an error message, print a stack backtrace, and exit with status
.ie n .IP "diag_ok( $bool\fR, \f(CW$name )" 4
.el .IP "diag_ok( \f(CW$bool\fR, \f(CW$name\fR )" 4
.IX Item "diag_ok( $bool, $name )"
Perform a test named '$name'. Test passes if \f(CW$bool\fR evaluates to true
.ie n .IP "diag_is($got, $expected\fR, \f(CW$name)" 4
.el .IP "diag_is($got, \f(CW$expected\fR, \f(CW$name\fR)" 4
.IX Item "diag_is($got, $expected, $name)"
Perform a test called '$name'. Test passes if \f(CW$got\fR eq \f(CW$expected\fR (yes,
that is a string comparison) and fails otherwise. This is a special
case of \f(CW$diag_ok\fR, but it produces much better output since the
function actually knows what is being compared.
.ie n .IP "diag_is_numeric($got, $expected\fR, \f(CW$name, [$tolerance])" 4
.el .IP "diag_is_numeric($got, \f(CW$expected\fR, \f(CW$name\fR, [$tolerance])" 4
.IX Item "diag_is_numeric($got, $expected, $name, [$tolerance])"
Same as diag_is except the comparison is numeric. If \f(CW$tolerance\fR is
specified, the test passes if \f(CW$got\fR is within \f(CW$tolerance\fR of \f(CW$expected\fR.
Prints the exit status and exits with that status. Exit status will
be 0 unless one or more tests have failed, in which case it will be 1.
projects / OpenSPARC-T2-DV / blob