First, thanks for testing this!
Here's the results for GNU/Linux, 2.6.18-1.2200.fc5smp (Fedora Core 5)
HIGH LEVEL COMMENTS
* The llvm-1.9.tar.gz file unpacks to a dir named "llvm". Shouldn't
that be llvm-1.9?
We have always labeled the dir just llvm which is fine. If you build llvm it will know its version 1.9.
* LLVM was built in Release mode in all cases
Thats the default, so thats good.
* I don't think this is ready for release. In particular the llvm-gcc4
seg faults on FC 5 for most of llvm-test programs.
* I'm going to re-try without using the binaries and building
everything from scratch.
Does llvm-gcc4 seg fault for make check? I've done extensive testing with llvm-gcc4 on x86 and did not have any problems with llvm-gcc4... so I am curious as to whats going on. If you could look into this, that would be great. Please triple check that you are using a clean llvm-test directory (ie. did not use llvm-gcc3 previously) and that the correct llvm-gcc is being used.
BUILD LLVM WITH GCC 4.1.1 20060525 (FAIL)
* DwarfWriter.cpp:2400: warning: overflow in implicit constant
Line looks like: EmitInt32(DW_CIE_ID); EOL("CIE Identifier
I don't know the code well enough to make a suggestion.
The run of llvm-test failed about 50%, some didn't even compile. I
running the whole thing as it was clear that GCC 4.1.1 (still)
We have noted in the Getting started guide that LLVM won't compile with gcc 4.1.1, so this is not a show stopper.
BUILD LLVM WITH GCC 3.4.6 WITH LLVM-GCC3 CONFIGURED (PASS)
* PASS: make, except these innocuous warnings from GCC 3.4.6 linker
(known 3.4.6 bug)
/proj/install/lib/gcc/i686-pc-linux-gnu/3.4.6/../../../../i686-pc-linux-gnu/bin/ld: `.gnu.linkonce.t._ZN4llvm11SCEVVisitorINS_12SCEVExpanderEPNS_5ValueEE5visitEPNS_4SCEVE' referenced in section `.rodata' of /proj/llvm/rel1.9/llvm/Release/lib/libLLVMAnalysis.a(ScalarEvolutionExpander.o): defined in discarded section `.gnu.linkonce.t._ZN4llvm11SCEVVisitorINS_12SCEVExpanderEPNS_5ValueEE5visitEPNS_4SCEVE' of /proj/llvm/rel1.9/llvm/Release/lib/libLLVMAnalysis.a(ScalarEvolutionExpander.o)
Right, thats fine.
* PASS: make install, except these doc linkage errors:
/usr/bin/pod2html: llvm-nm.pod: cannot resolve L<ar(1)> in
/usr/bin/pod2html: llvm-nm.pod: cannot resolve L<nm(1)> in
/usr/bin/pod2html: llvm-ar.pod: cannot resolve L<ar(1)> in
Please file a bug for this. This isn't a show stopper though.
* PASS: make check, except:
# of expected passes 1542
# of unexpected successes 1
# of expected failures 41
LLVM-TEST NIGHTLY WITH LLVM-GCC3 (FAIL)
This all looks pretty normal for llvm-gcc3. There are no plans to fix llvm-gcc3 problems/regressions with llvm-test. So not a show stopper.
BUILD LLVM WITH LLVM-GCC4 CONFIGURED (PASS/FAIL)
* Configure failed to find llvm-gcc4 when the directory provided to
was the llvm-gcc4-1.9-x86-linux directory unpacked from the tarball.
warning message at the end of configure run was produced. I don't
know what configure
is looking for, but its not finding it.
Interesting. This must be a bug in the configure script. This probably should be fixed.
* FAIL: 'make' failed in runtime library. Althought the runtime
library isn't needed
with llvm-gcc4, it shouldn't fail to compile it:
make: Entering directory
llvm: Compiling crtend.c for Release build (bytecode)
crtend.c:16: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://llvm.org/bugs> for instructions.
* PASS: 'make tools-only'
I'll have to defer to Chris on this and if its a show stopper.