The TIL/ML Compiler: Performance and Safety through Types (1996)
| Venue: | In Workshop on Compiler Support for Systems Software |
| Citations: | 39 - 9 self |
BibTeX
@INPROCEEDINGS{Morrisett96thetil/ml,
author = {Greg Morrisett and David Tarditi and Perry Cheng and Chris Stone and P. Cheng and Peter Lee and C. Stone and Robert Harper and P. Lee},
title = {The TIL/ML Compiler: Performance and Safety through Types},
booktitle = {In Workshop on Compiler Support for Systems Software},
year = {1996}
}
Years of Citing Articles
Bookmark
 |
 |
 |
 |
 |
 |
OpenURL
Abstract
Systems code requires both high performance and reliability. Usually, these two goals are at odds with each other. For example, to prevent kernel data structures from being over-written or read, either accidentally or maliciously, conventional systems use hardware-enforced protection or software fault isolation (SFI). Unfortunately, both of these techniques exact a cost at run time: Hardware protection requires expensive context switches and data copying to communicate with the kernel or other processes, whereas SFI requires run-time checks for loads, stores and jumps. Furthermore, these protection mechanisms only guarantee "read/write" safety and are often too weak to guarantee the integrity of a system. For instance, systems code must still verify at run time that a capability (i.e., file descriptor, port, message queue, etc.) is valid when using SFI or hardware protection.
Citations
No citations identified.
