Software Caching and Computation Migration in Olden

Carlisle, Martin C.; Rogers, Anne

doi:10.1006/jpdc.1996.0145

Cited by 34 publications

(34 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Table 2.1 presents a description of the programs in our benchmark suite. We analyze programs from the SPECjvm98 benchmark suite 11 and from the Java version of the Olden benchmark suite [52,51]. In addition, we analyze JLex, JavaCUP, and 205 raytrace.…”

Section: Resultsmentioning

confidence: 99%

Component Composition for Embedded Systems Using Semantic Aspect-Oriented Programming

Rinard¹

2004

View full text Add to dashboard Cite

The public reporting burden for this collection of information is estimated to average 1 hour per response, including the time for reviewing instructions, searching existing data sources, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing this burden, to Department of Defense, Washington Headquarters Services, Directorate for Information SPONSORING/MONITORING AGENCY REPORT NUMBER(S) AFRL-IF-WP-TR-2004-1568 DISTRIBUTION/AVAILABILITY STATEMENTApproved for public release; distribution is unlimited. SUPPLEMENTARY NOTES ABSTRACTThe goal of our research was to develop technologies and techniques in support of real-time systems for the defense community. Our research focused on Real-Time Java implementation and analysis techniques. Real-Time Java is important for the defense community because it holds out the promise of enabling developers to apply COTS Java technology to specialized military embedded systems. It also promises to allow the defense community to utilize a large Java-literate workforce for building defense systems.Our research has delivered several techniques that may make Real-Time Java a better platform for developing embedded systems. These techniques include ways to implement scoped memories (a key Real-Time Java construct) without the possibility of introducing unexpected and potentially catastrophic delays in the execution of real-time threads, analyses that ensure the correct use of Real-Time Java scoped memories, analyses that compute how much memory is required to execute a given Real-Time Java program (potentially helping developers calculate how much memory must be including in a given system to ensure that the system will execute without running out of memory), and optimizations that reduce the amount of memory required to execute a Real-Time Java program.

show abstract

Section: Resultsmentioning

confidence: 99%

Component Composition for Embedded Systems Using Semantic Aspect-Oriented Programming

Rinard¹

2004

View full text Add to dashboard Cite

show abstract

“…The main objective of our initial experiments is to show that our memory usage specification mechanism is expressive and that such an advanced form of type checking is viable. We converted to MEMJ a set of programs from the Java version of the Olden benchmark suite [7] and another set of smaller programs from the RegJava benchmark [11], before subjecting them to memory adequacy checking. Our initial experimental results are encouraging; however this is a proof-of-concept implementation and there is scope for optimization and more exhaustive experimentation.…”

Section: Methodsmentioning

confidence: 99%

Memory Usage Verification for OO Programs

et al. 2005

View full text Add to dashboard Cite

Abstract. We present a new type system for an object-oriented (OO) language that characterizes the sizes of data structures and the amount of heap memory required to successfully execute methods that operate on these data structures. Key components of this type system include type assertions that use symbolic Presburger arithmetic expressions to capture data structure sizes, the effect of methods on the data structures that they manipulate, and the amount of memory that methods allocate and deallocate. For each method, we conservatively capture the amount of memory required to execute the method as a function of the sizes of the method's inputs. The safety guarantee is that the method will never attempt to use more memory than its type expressions specify. We have implemented a type checker to verify memory usages of OO programs. Our experience is that the type system can precisely and effectively capture memory bounds for a wide range of programs.

show abstract

“…Four other examples have significant space reuse but have the same performance for all three kinds of region subtyping. However, we achieved significantly better space reuse for Reynolds3 and foo-sum when our inference is augmented with object/field region To check the scalability of our region inference, we converted a set of ten programs from the Olden benckmark set [11] to Core-Java, and measured their inference times, as shown in Fig 9. …”

Section: Methodsmentioning

confidence: 99%

Region inference for an object-oriented language

et al. 2004

View full text Add to dashboard Cite

Region-based memory management offers several important potential advantages over garbage collection, including real-time performance, better data locality, and more efficient use of limited memory. Researchers have advocated the use of regions for functional, imperative, and object-oriented languages. Lexically scoped regions are now a core feature of the Real-Time Specification for Java (RTSJ) [5].Recent research in region-based programming for Java has focused on region checking, which requires manual effort to augment the program with region annotations. In this paper, we propose an automatic region inference system for a core subset of Java. To provide an inference method that is both precise and practical, we support classes and methods that are region-polymorphic, with regionpolymorphic recursion for methods. One challenging aspect is to ensure region safety in the presence of features such as class subtyping, method overriding, and downcast operations. Our region inference rules can handle these object-oriented features safely without creating dangling references.

show abstract

Software Caching and Computation Migration in Olden

Cited by 34 publications

References 10 publications

Component Composition for Embedded Systems Using Semantic Aspect-Oriented Programming

Component Composition for Embedded Systems Using Semantic Aspect-Oriented Programming

Memory Usage Verification for OO Programs

Region inference for an object-oriented language

Contact Info

Product

Resources

About