🚀 go-pugleaf

Archive-name: auto/comp.compilers/New-TR-Rewriting-Executable-Files-to-Measure-Program-Behavior

A postscript copy of the following technical report is available for
anonymous ftp from primost.cs.wisc.edu in the file pub/rewriting-tr.ps.Z


	Rewriting Executable Files to Measure Program Behavior

		    James R. Larus and Thomas Ball
		     Computer Sciences Department
		       1210 West Dayton Street
		       University of Wisconsin
			  Madison, WI 53706

	      University of Wisconsin Computer Sciences
			Technical Report 1083

Inserting instrumentation code in a program is an effective technique for
measuring many aspects of program performance.  The instrumentation code
can be added at any stage of the compilation process by system tools such
as the compiler or linker or by external tools that are part of a
measurement system.  For a variety of reasons, adding this code after the
compilation process---by rewriting the executable file---is simpler and
more generally useful than adding it earlier.

This paper describes the problems that arose in writing the tools QP and
QPT, which add profiling and tracing code to programs on the MIPS and
SPARC processors. Many of these problems could have been avoided with
minor changes to compilers and executable files' symbol tables.  These
changes would simplify this technique for measuring program performance
and make it more generally useful.
-- 
Send compilers articles to compilers@iecc.cambridge.ma.us or
{ima | spdcc | world}!iecc!compilers.  Meta-mail to compilers-request.