[comp.arch] profiler changing source

andrew@frip.gwd.tek.com (Andrew Klossner) (01/16/88)

	"It seems to me that the best way to incorporate automatic
	profiling is to put profiling data back in the code. Otherwise,
	every time you compile a new version, you have to apply the
	profiler AGAIN."

Gack, no.  A common situation then would be that the profiler puts
optimization suggestions into the source, and a subsequent revision
changes the program in such a way that those suggestions become wrong
... but they're still there!

You don't need to recompile unless you've changed the source code, and
if you've changed the source code you can no longer trust old profiling
information.

  -=- Andrew Klossner   (decvax!tektronix!tekecs!andrew)       [UUCP]
                        (andrew%tekecs.tek.com@relay.cs.net)   [ARPA]