MDL: a language and compiler for dynamic program instrumentation
| Title | MDL: a language and compiler for dynamic program instrumentation |
| Publication Type | Conference Papers |
| Year of Publication | 1997 |
| Authors | Hollingsworth J, Niam O, Miller BP, Xu Z, Goncalves MJR, Zheng L |
| Conference Name | , 1997 International Conference on Parallel Architectures and Compilation Techniques., 1997. Proceedings |
| Date Published | 1997/11/10/14 |
| Publisher | IEEE |
| ISBN Number | 0-8186-8090-3 |
| Keywords | Alpha architecture, application program, application program interfaces, Application software, compiler generators, Computer science, dynamic code generation, Dynamic compiler, dynamic program instrumentation, Educational institutions, files, instrumentation code, Instruments, MDL, measurement, message channels, Message passing, Metric Description Language, modules, nodes, Operating systems, optimising compilers, PA-RISC, Paradyn Parallel Performance Tools, Parallel architectures, parallel programming, performance data, platform independent descriptions, Power 2 architecture, Power generation, procedures, program debugging, Program processors, running programs, Runtime, software metrics, SPARC, Specification languages, x86 architecture |
| Abstract | We use a form of dynamic code generation, called dynamic instrumentation, to collect data about the execution of an application program. Dynamic instrumentation allows us to instrument running programs to collect performance and other types of information. The instrumentation code is generated incrementally and can be inserted and removed at any time. Our instrumentation currently runs on the SPARC, PA-RISC, Power 2, Alpha, and x86 architectures. Specification of what data to collect are written in a specialized language called the Metric Description Language, that is part of the Paradyn Parallel Performance Tools. This language allows platform independent descriptions of how to collect performance data. It also provides a concise way to specify, how to constrain performance data to particular resources such as modules, procedures, nodes, files, or message channels (or combinations of these resources). We also describe the details of how we weave instrumentation into a running program |
| DOI | 10.1109/PACT.1997.644016 |