Proceedings of 30th Annual International Symposium on Microarchitecture
DOI: 10.1109/micro.1997.645816
|View full text |Cite
|
Sign up to set email alerts
|

Value profiling

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

3
94
0

Publication Types

Select...
5
2
1

Relationship

0
8

Authors

Journals

citations
Cited by 107 publications
(101 citation statements)
references
References 9 publications
3
94
0
Order By: Relevance
“…al note that instructions other than loads may be highly invariant [4]. For example, consider the following code:…”
Section: Goal-directed Value Profilingmentioning
confidence: 99%
See 1 more Smart Citation
“…al note that instructions other than loads may be highly invariant [4]. For example, consider the following code:…”
Section: Goal-directed Value Profilingmentioning
confidence: 99%
“…We then compute our threshold by subtracting this minimum count from the execution frequency of p. We know that if the count of the other field ever exceeds this threshold, then the optimizer can not select this value for specialization (since count(v) can not be high enough) 4 . This means, that if the other threshold is exceeded, we should stop profiling this point, since it will no longer be selected for optimization.…”
Section: Dynamic Elimination Of Unprofitable Candidatesmentioning
confidence: 99%
“…The approaches in [4][9] use profiling to detect frequent loops to map to a special address region that an architecture would then map to a small low-power loop cache, while the approach in [12] compresses those regions to reduce memory traffic and hence power. The approach in [6] profiles values of variables or subroutine parameters to detect pseudo-constants that can aid a compiler in optimizing for performance, or even for reduced energy [7].…”
Section: Introductionmentioning
confidence: 99%
“…A similar situation holds in partial evaluation, where a variable has to be static in order to permit specialization [15]. In practice, it is often the case that an expression at a point in a program "almost always" takes on a particular value [6]. As an example, in the SPEC-95 benchmark perl, the function memmove is called close to 24 million times.…”
Section: Introductionmentioning
confidence: 99%