Proceedings of the ACM SIGPLAN 1994 Conference on Programming Language Design and Implementation 1994
DOI: 10.1145/178243.178260
|View full text |Cite
|
Sign up to set email alerts
|

Atom

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
6
0

Year Published

1999
1999
2024
2024

Publication Types

Select...
8
1

Relationship

0
9

Authors

Journals

citations
Cited by 606 publications
(16 citation statements)
references
References 4 publications
0
6
0
Order By: Relevance
“…To compare these algorithms, we implemented both, as well as some variants, and used the ATOM tool [28] to measure the number of processor cycles spent in computing an optimal path [19]. We ran a series of tests on a multicalendar granularity graph similar to that shown in Fig.…”
Section: Choosing the Methodsmentioning
confidence: 99%
“…To compare these algorithms, we implemented both, as well as some variants, and used the ATOM tool [28] to measure the number of processor cycles spent in computing an optimal path [19]. We ran a series of tests on a multicalendar granularity graph similar to that shown in Fig.…”
Section: Choosing the Methodsmentioning
confidence: 99%
“…First, static methods incur compilation or modification overhead at the time they are applied, which can be large in some tools. For example, while ATOM took less than 10 seconds in most cases to instrument each of the SPEC92 benchmark suite on even old systems like Digital Alpha AXP 3000 Model, the AspectJ 1.1 compiler has been reported to slow down the compilation step by almost 5 times compared to the javac 1.4 reference compiler for inserting 10 different logging aspect codes . Second, there is a runtime overhead in intercepting existing function calls and handling the control of the intercepted calls.…”
Section: Issues In Fci Techniquesmentioning
confidence: 99%
“…The programs were generated with the Compaq f77 compiler, applying full optimizations, for an AlphaStation 600 5/266. The traces were obtained by instrumenting the binaries with the ATOM tool [33]. Since the simulator is very slow, due to the detail of the simulations, we run only a portion of 100 M (million) instructions of each benchmark, after skipping an initial start-up phase.…”
Section: Experimental Frameworkmentioning
confidence: 99%