2011 17th IEEE Real-Time and Embedded Technology and Applications Symposium 2011
DOI: 10.1109/rtas.2011.29
|View full text |Cite
|
Sign up to set email alerts
|

Predictable Binary Code Cache: A First Step towards Reconciling Predictability and Just-in-Time Compilation

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2012
2012
2013
2013

Publication Types

Select...
1
1

Relationship

0
2

Authors

Journals

citations
Cited by 2 publications
(3 citation statements)
references
References 21 publications
0
3
0
Order By: Relevance
“…Therefore, also a data flow analysis is used to model the content of the D-ISP with the STACK replacement policy. For LRU only analysis methods that assume memory entities of a unique size [5], [23] are known, but the authors are not aware of any LRU analysis that is able to handle functions of different size. Therefore, a data flow analysis tracking all possible D-ISP states is also used for the LRU replacement policy.…”
Section: Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“…Therefore, also a data flow analysis is used to model the content of the D-ISP with the STACK replacement policy. For LRU only analysis methods that assume memory entities of a unique size [5], [23] are known, but the authors are not aware of any LRU analysis that is able to handle functions of different size. Therefore, a data flow analysis tracking all possible D-ISP states is also used for the LRU replacement policy.…”
Section: Discussionmentioning
confidence: 99%
“…In [23] two structures of a method cache for just-in-time (JIT) compilers are proposed and statically analyzed. One uses a fixed block size for all functions, whereas the other structure fixes the layout of the functions in the cache.…”
Section: Related Workmentioning
confidence: 99%
“…Our experiments so far had only modest space requirements for recompilation (11-144KB per benchmark for SPECint2006). In addition, since in our approach nonrecompiled code is already available in native form and executes in parallel to recompilation, our system doesn't rely on smart code caching as heavily as other dynamic compilation systems that try to avoid slow, interpreted code execution [Hazelwood and Smith 2004;Bouakaz et al 2011].…”
Section: The Runtime Managermentioning
confidence: 99%