Abstract

If a compiler for language L is implemented in L, then it should be able to compile itself. But for systems used interactively, commands are compiled and immediately executed, and these commands may invoke the compiler, there is the question of how ever to cross-compile for another architecture. Also, where the compiler writes binary files of static type information that must then be read in by the bootstrapped interactive compiler, how can one ever change the format of digested type information in binary files? Here I attempt an axiomatic clarification of the bootstrapping technique. I use the Standard ML of New Jersey as a case study. This should be useful to implementors of any self-applicable interactive compiler with nontrivial object-file and runtime-system compatibility problems. 1 Introduction A conventional C compiler, written in C, is said to be "bootstrapped" if it compiles itself. Now, suppose a new version of the compiler source is written, that uses different registers...

Citations