footprints man page on HP-UX

Printed from http://www.polarhome.com/service/man/?qf=footprints&af=0&tf=2&of=HP-UX

footprints(1)							 footprints(1)

NAME
       footprints - summarize information from compiler footprint records

SYNOPSIS
       filename...

DESCRIPTION
       The  command  scans the named object files, analyzes the compiler foot‐
       print records stored in those files, and generates  a  summary  report.
       This  report  is	 intended  for	use by HP support and lab engineers to
       assist in problem diagnosis.

       The report contains the following information:

	      ·	 Total number of compilation units found.

	      ·	 Earliest and latest compiler timestamp, and the linker	 time‐
		 stamp (if available).

	      ·	 Total size of text and data segments.

	      ·	 List  of  compiler  versions used, with number of compilation
		 units compiled with each version.

	      ·	 List of options used, with number of compilation  units  com‐
		 piled	with each option setting.  This list is separated into
		 two groups, with the most interesting options	in  the	 first
		 group,	 followed by all remaining options alphabetized in the
		 second group.

       The following file types are recognized:

	      ·	 Executable files and shared libraries.

		 The command will attempt to find  all	dependent,  non-system
		 shared	 libraries  and	 will print a separate report for each
		 shared library.  If the or environment variable  is  set,  it
		 will search for dependent libraries in the directories listed
		 in the environment variable (if is set, will be ignored).  It
		 will  also  use  the embedded search path in the object file.
		 If a shared library cannot be located, a diagnostic  will  be
		 printed and execution will continue.

	      ·	 Archive libraries.

		 The command will scan each object file member of the archive.

	      ·	 Relocatable object files.

		 The command will scan the named object files.

       The command supports SOM and ELF object file formats, 32-bit and 64-bit
       code, and PA-RISC and Integrity systems.	 It  supports  compiler	 foot‐
       prints  produced by the HP C and C++ compilers.	Compilation units pro‐
       duced by other compilers may not be reflected in the summary.

   Options
       The command recognizes the following options:

	      Print the version number and quit.

	      Verbose mode: prints detail information about  each  compilation
	      unit found.

	      Prints warnings for possible compatibility problems.
		   Currently,  it  prints  a warning for any compilation units
		   built for Integrity systems with a C/C++  compiler  earlier
		   than	 Version A.05.50.  Warnings are printed to stderr with
		   three asterisks at the beginning of the line.

EXAMPLES
       The following example shows the beginning of a typical summary report:

	      Scanning /usr/bin/ksh ...

	      Compiler footprint summary

	      Number of compilation units:    51

	      Earliest compiler timestamp:    N/A
	      Latest compiler timestamp:      N/A
	      Linker timestamp:	      15-Jul-2006 13:07 UTC

	      Total size:  425.8K (text)  24.8K (data)

	      version		      [A.06.11/ANSI C	51]
	      architecture	      [ipf32	  51]
	      -O		      [01	   1] [02     50]
	      PBO		      [off	  51]
	      -g		      [off	  51]
	      debugopt		      [off	  51]

	      +Ointeger_overflow      [moderate	  51]
	      +Olit		      [const	  51]
	      +eh		      [off	  51]
	      -fpeval		      [float	  51]
	      -inline		      [1	   1] [2      50]
	      -link_type	      [dynamic	  51]
	      -mt		      [(off)	  51]
	      -rodata		      [cond	  51]
	      ...

       The line shows that all 51 compilation units were compiled with Version
       A.06.11	of  the	 ANSI C compiler.  The line shows that the application
       was compiled for Integrity systems (Itanium(R) Product Family)  in  the
       32-bit data model.

       The  line  shows	 that one compilation unit was compiled at the default
       level of optimization (level 01), and the other	50  were  compiled  at
       level 02.  According to the line, all 51 were compiled without profile-
       based optimization.

       The line shows that no compilation units were compiled  with  the  sym‐
       bolic  debug option.  Otherwise, the line would show the number of com‐
       pilation units compiled with various combinations of symbolic debug and
       higher optimization levels.

       For  on/off  options  like  settings  listed in parentheses represent a
       default setting not overridden by a compiler option.

       Many of the options in the footprint record do not correspond  directly
       to  a  command-line  compiler switch, or have a different spelling, and
       are included in this report for use by HP support  and  lab  engineers.
       See cc(1) for a description of supported command-line switches.

AUTHOR
       was developed by HP.

SEE ALSO
       cc(1), elfdump(1), odump(1).

								 footprints(1)
[top]

List of man pages available for HP-UX

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net