Re: Instrumenting code for profiling.

nmm1@cus.cam.ac.uk (Nick Maclaren)
19 Nov 2004 00:48:03 -0500

          From comp.compilers
Related articles
Instrumenting code for profiling. par_ianth@yahoo.com (2004-11-14)
Re: Instrumenting code for profiling. gah@ugcs.caltech.edu (glen herrmannsfeldt) (2004-11-17)
Re: Instrumenting code for profiling. s.bosscher@student.tudelft.nl (2004-11-17)
Re: Instrumenting code for profiling. nmm1@cus.cam.ac.uk (2004-11-19)
Re: Instrumenting code for profiling. diablovision@yahoo.com (2004-11-20)
Re: Instrumenting code for profiling. idbaxter@semdesigns.com (Ira Baxter) (2004-11-20)
Re: Instrumenting code for profiling. tmk@netvision.net.il (2004-11-20)
Re: Instrumenting code for profiling. nmm1@cus.cam.ac.uk (2004-11-26)
| List of all articles for this month |
From: nmm1@cus.cam.ac.uk (Nick Maclaren)
Newsgroups: comp.compilers
Date: 19 Nov 2004 00:48:03 -0500
Organization: University of Cambridge, England
References: 04-11-043 04-11-051
Keywords: debug, performance
Posted-Date: 19 Nov 2004 00:48:03 EST

glen herrmannsfeldt <gah@ugcs.caltech.edu> writes:
|>
|> FETE would read in a Fortran 66 program and then write out a new
|> Fortran program that would count the number of times each statement
|> was executed. ...


Yes. There were other, similar ones, too.


|> Presumably a similar system could be done for other languages.


If you can't, it would be pretty hard to compile! With Fortran or
BCPL, you could take short cuts and not do a full parsing job; with C
or Algol 68, you would have to do a full parse, and would find it
easiest to hack a compiler.


Regards,
Nick Maclaren.

Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.