Do the llvm nightly scripts "recurse" the compiler or just test that it can self host itself?
On Jun 19, 2012, at 5:24 PM, reed kotler <rkotler at mips.com> wrote:> Do the llvm nightly scripts "recurse" the compiler or just test that it > can self host itself? >No idea what you mean here. Can you explain? -eric
Eric Christopher <echristo at apple.com> writes:> On Jun 19, 2012, at 5:24 PM, reed kotler <rkotler at mips.com> wrote: > >> Do the llvm nightly scripts "recurse" the compiler or just test that it >> can self host itself? >> > > No idea what you mean here. Can you explain?Step 1: compile Clang with some other compiler (i.e. gcc or old Clang) Step 2: compile Clang with the binaries produced on step 1 Step 3: compile Clang with the binaries produced on step 2 I think he means Step 3.
On 06/27/2012 05:00 PM, Eric Christopher wrote:> On Jun 19, 2012, at 5:24 PM, reed kotler<rkotler at mips.com> wrote: > >> Do the llvm nightly scripts "recurse" the compiler or just test that it >> can self host itself? >> > No idea what you mean here. Can you explain? > > -ericrecursing a compiler means this. clang/llvm source == src compile src using clang/llvm (which may have been built using gcc) -> clang/llvm' (prime) compile src using clang/llvm' -> clang/llvm'' verify that the binaries for clang/llvm' == binaries for clang/llvm'' A compiler can be self hosted (made using itself) by just producing clang/llvm' That is not as strong a test as recursing the compiler, even though you might run the full test suite using clang/llvm"