STACKUSE(CP) XENIX System V STACKUSE(CP)
Name
stackuse - Determines stack requirements for C programs.
Syntax
stackuse [ -m startsym ] [ -r fakeref ] [ -s libstack ] [ -a
] file ...
Description
stackuse determines the stack requirements of one or more C
language programs. It displays the name of the main routine
in a file, its stack requirements in bytes, and the number
of recursive routines. All command line switches are
optional.
-mstartsym Prints only the specified start (``main'')
symbol. If this option is not specified all
start symbols (those which are not called by
anybody) will be printed.
-rfakeref Uses the named file fakeref as a fake
references file. The format is: parent child
. The special parent .LEAF is a meta-parent
meaning all leaf nodes.
-slibstack Uses the named file as library of costs for
external routines. The format is: subr
stack. The special subr .UNDEF is a meta-
subroutine meaning all undefined routines.
-a Prints data for all symbols, not just start
symbols.
The -r and -s options may be repeated an arbitrary number of
times. The effect is additive rather than destructive. In
the case of duplicate definitions, the first is used.
Lines of the -r and -s files which begin with a pound sign
(#) are treated as comments and otherwise are ignored.
Files
/usr/lib/stackuse/* Passes, libraries
/tmp/* Temporaries used by passes.
Page 1 (printed 8/7/87)
STACKUSE(CP) XENIX System V STACKUSE(CP)
Diagnostics
Usage (fatal).
Redefinitions in -r, -s files, or in the source (warning).
Presence of routines for which no stack value is provided
(warning).
Notes
For the libstack and fakeref files, a comment character (#)
is used.
Page 2 (printed 8/7/87)
