Checking System Rules Using System-Specific, Programmer-Written Compiler Extensions

(October 2000)

View FullText article

CiteSeer (at Penn State), CiteSeer (at MIT), CiteSeer (at Zurich), CiteSeer (at Singapore)

Reviews [Write a review of this article]

There are no reviews of this article

Notes for this article

srccheck has 1 private note and 0 public notes for this article. If you are srccheck then you can log in to see the private note.

Find related articles from these CiteULike users

pedagand, srccheck

Find related articles with these CiteULike tags

defects, mc, meta-compilation, osdi00, project-master-thesis, tools

Abstract

Systems software such as OS kernels, embedded systems, and libraries must obey many rules for both correctness and performance. Common examples include "accesses to variable A must be guarded by lock B," "system calls must check user pointers for validity before using them," and "message handlers should free their buffers as quickly as possible to allow greater parallelism." Unfortunately, adherence to these rules is largely unchecked...

@inproceedings{citeulike:2340127, abstract = {Systems software such as OS kernels, embedded systems, and libraries must obey many rules for both correctness and performance. Common examples include \"accesses to variable A must be guarded by lock B,\" \"system calls must check user pointers for validity before using them,\" and \"message handlers should free their buffers as quickly as possible to allow greater parallelism.\" Unfortunately, adherence to these rules is largely unchecked...}, author = {Engler, D. and Chelf, B. and Chou, A. and Hallem, S. }, booktitle = {Proceedings of the Fourth Symposium on Operating Systems Design and Implementation, San Diego, CA}, citeulike-article-id = {2340127}, keywords = {defects, mc, osdi00, tools}, month = {October}, posted-at = {2008-02-06 10:34:50}, priority = {0}, title = {Checking System Rules Using System-Specific, Programmer-Written Compiler Extensions}, url = {http://citeseer.ist.psu.edu/engler00checking.html}, year = {2000} }

RIS record

TY - CONF ID - citeulike:2340127 L3 - citeulike-article-id:2340127 N2 - Systems software such as OS kernels, embedded systems, and libraries must obey many rules for both correctness and performance. Common examples include "accesses to variable A must be guarded by lock B," "system calls must check user pointers for validity before using them," and "message handlers should free their buffers as quickly as possible to allow greater parallelism." Unfortunately, adherence to these rules is largely unchecked... TI - Checking System Rules Using System-Specific, Programmer-Written Compiler Extensions T2 - Proceedings of the Fourth Symposium on Operating Systems Design and Implementation, San Diego, CA KW - defects KW - mc KW - osdi00 KW - tools AU - Engler, D AU - Chelf, B AU - Chou, A AU - Hallem, S PY - 2000/October// UR - http://citeseer.ist.psu.edu/engler00checking.html ER -

RIS BibTeX