A garbage-collecting typed assembly language

Hawblitzel, Chris; Huang, Heng; Wittie, Lea; Chen, Juan

doi:10.1145/1190315.1190323

Cited by 6 publications

(3 citation statements)

References 31 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Therefore, we have developed a type system that supports both LIL C the state of memory [11]. Using this type system, the garbage collector can statically prove that its deallocation operations are safe.…”

Section: Typed Assembly Languagementioning

confidence: 99%

Singularity

Hunt

Larus

2007

SIGOPS Oper. Syst. Rev.

216

View full text Add to dashboard Cite

Every operating system embodies a collection of design decisions. Many of the decisions behind systems have remained unchanged, even as hardware and software have evolved. Operating systems form the foundation of almost every software stack, so inadequacies in present systems have a pervasive impact. This paper describes the efforts of the Singularity project to re-examine these design choices in light of advances in programming languages and verification tools. Singularity systems incorporate three key architectural features: software-isolated processes for protection of programs and system services, contract-based channels for communication, and manifest-based programs for verification of system properties. We describe this foundation in detail and sketch the ongoing research in experimental systems that build upon it.

show abstract

Section: Typed Assembly Languagementioning

confidence: 99%

Singularity

Hunt

Larus

2007

SIGOPS Oper. Syst. Rev.

216

View full text Add to dashboard Cite

show abstract

“…Clearly, adding a garbage collector to the infrastructure will require additional certification effort, but this is, hopefully, a one time cost. Furthermore we are encouraged by a number of projects looking at provably correct garbage collection techniques (see for instance [11,27]). …”

Section: Introductionmentioning

confidence: 99%

Garbage collection for safety critical Java

Schoeberl

Vítek

2007

Proceedings of the 5th International Workshop on Java Technologies for Real-Time and Embedded Systems - JTRES '07

View full text Add to dashboard Cite

The Real-time Specification for Java and the upcoming, and more restricted, Safety Critical Java standard have been designed to allow programmers to avoid pauses caused by automatic memory management algorithms. Dynamic memory is user-managed using a region-based allocation scheme known as scoped memory areas. However, usage of those scoped memories is cumbersome and often leads to runtime errors. In this paper we focus on the safety critical subset of the Real-time Specification for Java and propose a real-time garbage collector that can be scheduled like a normal real-time thread with a deadline monotonic assigned priority. The restricted programming model offered by Safety Critical Java allows us to substantially simplify the collector. Our proposal has been implemented and evaluated in the context of the JOP project. JOP is a Java processor especially designed for embedded real-time systems. The architecture is optimized for worst-case execution time (WCET) instead of the usual optimization for average case execution time. Execution time of bytecodes is known cycle accurate.

show abstract

“…GTAL [11] uses a linear type system to encode new types from individual memory words. By building up appropriate abstractions, GTAL is capable of type-checking a variety of garbage collection mechanisms.…”

Section: Introductionmentioning

confidence: 99%