Re: Instrumenting code for profiling.

"Ira Baxter" <idbaxter@semdesigns.com>
20 Nov 2004 21:29:50 -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: "Ira Baxter" <idbaxter@semdesigns.com>
Newsgroups: comp.compilers
Date: 20 Nov 2004 21:29:50 -0500
Organization: http://extra.newsguy.com
References: 04-11-043
Keywords: debug, performance
Posted-Date: 20 Nov 2004 21:29:50 EST

"PK" <par_ianth@yahoo.com> wrote


> I had a question regarding how compilers do instrumentation to
> collect profile information. Specifically, how do compilers handle the
> part of mapping the collected profile back to the original program
> (which is without the instrumentation). ...


I don't know how it is done in commercial compilers.


We do it by instrumenting the source code with profiling probes, using
full language parsers for each language to enable us to capture
accurate source line information and associate it with the probe.
This works very well indeed for our present set of profiling tools for
C, C++, COBOL, Java, and C#.


The technical details can be found in a white paper
at http://www.semdesigns.com/Products/TestCoverage


--
Ira D. Baxter, Ph.D., CTO 512-250-1018
Semantic Designs, Inc. www.semdesigns.com

Post a followup to this message

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