AbstractPassing compilers through themselves is a well known technique whose major benefit is that any improvement in code generation will result in an improved compiler. Previous reports of work in this area have mentioned that it is possible to validate the compiler by running the compiler through itself a second time and comparing the resulting binary files. This paper is designed to clarify this technique which has received little attention and is often misleadingly described.