More on backend testing

Ok, I'm slowly making my backend understand stuff in
test/Programs/SingleSource/UnitTests. I can convert the first test to
assembler, compile it and run.

The only thing I don't see if the expected outputs from the tests -- so that I
don't need to look at each test and figure out what it should output. Is it
true such expected outputs are not available? I not, I'll probably do some
automation myself.

- Volodya

Vladimir Prus wrote:

Ok, I'm slowly making my backend understand stuff in test/Programs/SingleSource/UnitTests. I can convert the first test to assembler, compile it and run.

The only thing I don't see if the expected outputs from the tests -- so that I don't need to look at each test and figure out what it should output. Is it true such expected outputs are not available? I not, I'll probably do some automation myself.

- Volodya

_______________________________________________
LLVM Developers mailing list
LLVMdev@cs.uiuc.edu http://llvm.cs.uiuc.edu
http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev

The reference output for the LLVM test suite is generated by compiling the test program with the native GCC compiler and running it. The test suite then compiles the program using the LLVM compilers, runs the program, and compares the LLVM program's output to the native program's output.

In short, we assume that native GCC compiles the program correctly and then compare LLVM against it.

-- John T.

John Criswell wrote:

The reference output for the LLVM test suite is generated by compiling
the test program with the native GCC compiler and running it. The test
suite then compiles the program using the LLVM compilers, runs the
program, and compares the LLVM program's output to the native program's
output.

In short, we assume that native GCC compiles the program correctly and
then compare LLVM against it.

Thanks, John! This approach is very nice.

- Volodya