Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pxp(1) [bsd man page]

PXP(1)							      General Commands Manual							    PXP(1)

NAME
pxp - Pascal execution profiler SYNOPSIS
pxp [ -acdefjnstuw_ ] [ -23456789 ] [ -z [ name ... ] ] name.p DESCRIPTION
Pxp can be used to obtain execution profiles of Pascal programs or as a pretty-printer. To produce an execution profile all that is neces- sary is to translate the program specifying the z option to pi or pix, to execute the program, and to then issue the command pxp -z name.p A reformatted listing is output if none of the c, t, or z options are specified; thus pxp old.p > new.p places a pretty-printed version of the program in `old.p' in the file `new.p'. The use of the following options of pxp is discussed in sections 2.6, 5.4, 5.5 and 5.10 of the Berkeley Pascal User's Manual. -a Print the bodies of all procedures and functions in the profile; even those which were never executed. -c Extract profile data from the file core. -d Include declaration parts in a profile. -e Eliminate include directives when reformatting a file; the include is replaced by the reformatted contents of the specified file. -f Fully parenthesize expressions. -j Left justify all procedures and functions. -n Eject a new page as each file is included; in profiles, print a blank line at the top of the page. -s Strip comments from the input text. -t Print a table summarizing procedure and function call counts. -u Card image mode; only the first 72 characters of input lines are used. -w Suppress warning diagnostics. -z Generate an execution profile. If no names, are given the profile is of the entire program. If a list of names is given, then only any specified procedures or functions and the contents of any specified include files will appear in the profile. -_ Underline keywords. -d With d a digit, 2 <= d <= 9, causes pxp to use d spaces as the basic indenting unit. The default is 4. FILES
name.p input file name.i include file(s) pmon.out profile data core profile data source with -c /usr/share/pascal/how_pxpinformation on basic usage SEE ALSO
Berkeley Pascal User's Manual pi(1), px(1) DIAGNOSTICS
For a basic explanation do pxp Error diagnostics include `No profile data in file' with the c option if the z option was not enabled to pi; `Not a Pascal system core file' if the core is not from a px execution; `Program and count data do not correspond' if the program was changed after compilation, before profiling; or if the wrong program is specified. AUTHOR
William N. Joy BUGS
Does not place multiple statements per line. 3rd Berkeley Distribution PXP(1)

Check Out this Related Man Page

PI(1)							      General Commands Manual							     PI(1)

NAME
pi - Pascal interpreter code translator SYNOPSIS
pi [ -blnpstuwz ] [ -i name ... ] name.p DESCRIPTION
Pi translates the program in the file name.p leaving interpreter code in the file obj in the current directory. The interpreter code can be executed using px. Pix performs the functions of pi and px for `load and go' Pascal. The following flags are interpreted by pi; the associated options can also be controlled in comments within the program as described in the Berkeley Pascal User's Manual. -b Block buffer the file output. -i Enable the listing for any specified procedures and functions and while processing any specified include files. -l Make a program listing during translation. -n Begin each listed include file on a new page with a banner line. -p Suppress the post-mortem control flow backtrace if an error occurs; suppress statement limit counting. -s Accept standard Pascal only; non-standard constructs cause warning diagnostics. -t Suppress runtime tests of subrange variables and treat assert statements as comments. -u Card image mode; only the first 72 characters of input lines are used. -w Suppress warning diagnostics. -z Allow execution profiling with pxp by generating statement counters, and arranging for the creation of the profile data file pmon.out when the resulting object is executed. FILES
file.p input file file.i include file(s) /usr/share/pascal/pi_stringstext of the error messages /usr/share/pascal/how_pi*basic usage explanation obj interpreter code output SEE ALSO
Berkeley Pascal User's Manual pcc(1), pix(1), px(1), pxp(1), pxref(1) DIAGNOSTICS
For a basic explanation do pi In the diagnostic output of the translator, lines containing syntax errors are listed with a flag indicating the point of error. Diagnos- tic messages indicate the action which the recovery mechanism took in order to be able to continue parsing. Some diagnostics indicate only that the input is `malformed.' This occurs if the recovery can find no simple correction to make the input syntactically valid. Semantic error diagnostics indicate a line in the source text near the point of error. Some errors evoke more than one diagnostic to help pinpoint the error; the follow-up messages begin with an ellipsis `...'. The first character of each error message indicates its class: EFatal error; no code will be generated. eNon-fatal error. wWarning - a potential problem. sNon-standard Pascal construct warning. If a severe error occurs which inhibits further processing, the translator will give a diagnostic and then `QUIT'. AUTHORS
Charles B. Haley, William N. Joy, and Ken Thompson BUGS
Formal parameters which are procedures and functions are not supported. The keyword packed and the function dispose are recognized but have no effect. For clarity, semantic errors should be flagged at an appropriate place in the source text, and multiple instances of the `same' semantic error should be summarized at the end of a procedure or function rather than evoking many diagnostics. When include files are present, diagnostics relating to the last procedure in one file may appear after the beginning of the listing of the next. 3rd Berkeley Distribution PI(1)
Man Page

Featured Tech Videos