1989
DOI: 10.1007/bf00243134
|View full text |Cite
|
Sign up to set email alerts
|

A mechanically verified code generator

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
17
0

Year Published

1990
1990
2010
2010

Publication Types

Select...
6
2

Relationship

0
8

Authors

Journals

citations
Cited by 55 publications
(17 citation statements)
references
References 11 publications
0
17
0
Order By: Relevance
“…Two significant instances are Young's [95] work, using the Boyer-Moore theorem prover, and Joyce's [30,29] work using the HOL system. In both cases, the target code of the translation is a nonidealized machine-level architecture whose implementation has been verified with respect to a low level of the computer, see for example [27,42].…”
Section: Compiler Correctness Proofsmentioning
confidence: 99%
“…Two significant instances are Young's [95] work, using the Boyer-Moore theorem prover, and Joyce's [30,29] work using the HOL system. In both cases, the target code of the translation is a nonidealized machine-level architecture whose implementation has been verified with respect to a low level of the computer, see for example [27,42].…”
Section: Compiler Correctness Proofsmentioning
confidence: 99%
“…Working with the Boyer-Moore theorem prover [2] the researchers of the CLI stack project succeeded as early as 1989 to prove formally the correctness of a system which provided the following components: a non pipelined processor [3], an assembler [4], a compiler for a simple imperative language [5], a rudimentary operating system kernel [6] written in machine language. This kernel provided scheduling for a fixed number of processes; each process had the right to access a fixed interval of addresses in the processor's physical memory.…”
Section: The Challenge Of Verifying Entire Systemsmentioning
confidence: 99%
“…We feel that the size alone of the specifications calls for automatic proof checking. Recent attempts to automatically check a compiler correctness proof are reported by Young [46] and Joyce [9,8]. For now, however, we leave the automatic checking of the Cantor correctness proof to future work and turn to a performance evaluation.…”
Section: Compiling Action Notationmentioning
confidence: 99%