[LLVMdev] 1.9 Prerelease Available for Testing (TAKE TWO)

Reid Spencer rspencer at reidspencer.com
Fri Nov 17 08:19:44 PST 2006 

Hi Tanya,

Here's my second attempt on Fedora Core 5.  The changes this time are:

1. Using GCC 4.0.3 as the compiler
2. Building everything from source (no pre-built binaries used)

BUILD LLVM WITH GCC 4.0.3
  * No issues, just the usual warnings.

BUILD LLVM-GCC WITH GCC 4.0.3
  * No issues

RUN LLVM-TEST WITH GCC 4.0.3
  * The following failures were encountered. Some of them are
explainable:

TEST-FAIL: llc /SingleSource/UnitTests/Vector/SSE/sse.expandfft
TEST-FAIL: jit /SingleSource/UnitTests/Vector/SSE/sse.expandfft
TEST-FAIL: llc /SingleSource/UnitTests/Vector/SSE/sse.isamax
TEST-FAIL: jit /SingleSource/UnitTests/Vector/SSE/sse.isamax
TEST-FAIL: jit /SingleSource/UnitTests/Vector/SSE/sse.stepfft
TEST-FAIL: cbe /SingleSource/UnitTests/Vector/build2
TEST-FAIL: cbe /SingleSource/UnitTests/Vector/build
TEST-FAIL: cbe /SingleSource/UnitTests/Vector/divides
TEST-FAIL: jit /SingleSource/UnitTests/Vector/multiplies
TEST-FAIL: cbe /SingleSource/UnitTests/Vector/multiplies
TEST-FAIL: cbe /SingleSource/UnitTests/Vector/simple
TEST-FAIL: cbe /SingleSource/UnitTests/Vector/sumarray
TEST-FAIL: cbe /SingleSource/UnitTests/Vector/sumarray-dbl
  * The above tests fail due to either lack of SSE3 hardware on my
machine or
    lack of support for vector types in my compiler.

TEST-FAIL: llc /SingleSource/Regression/C++/EH/ctor_dtor_count-2
TEST-FAIL: jit /SingleSource/Regression/C++/EH/ctor_dtor_count-2
TEST-FAIL: cbe /SingleSource/Regression/C++/EH/ctor_dtor_count-2
TEST-FAIL: llc /SingleSource/Regression/C++/EH/ctor_dtor_count
TEST-FAIL: jit /SingleSource/Regression/C++/EH/ctor_dtor_count
TEST-FAIL: cbe /SingleSource/Regression/C++/EH/ctor_dtor_count
TEST-FAIL: llc /SingleSource/Regression/C++/EH/exception_spec_test
TEST-FAIL: jit /SingleSource/Regression/C++/EH/exception_spec_test
TEST-FAIL: cbe /SingleSource/Regression/C++/EH/exception_spec_test
TEST-FAIL: llc /SingleSource/Regression/C++/EH/function_try_block
TEST-FAIL: jit /SingleSource/Regression/C++/EH/function_try_block
TEST-FAIL: cbe /SingleSource/Regression/C++/EH/function_try_block
TEST-FAIL: llc /SingleSource/Regression/C++/EH/simple_rethrow
TEST-FAIL: jit /SingleSource/Regression/C++/EH/simple_rethrow
TEST-FAIL: cbe /SingleSource/Regression/C++/EH/simple_rethrow
TEST-FAIL: llc /SingleSource/Regression/C++/EH/simple_throw
TEST-FAIL: jit /SingleSource/Regression/C++/EH/simple_throw
TEST-FAIL: cbe /SingleSource/Regression/C++/EH/simple_throw
TEST-FAIL: llc /SingleSource/Regression/C++/EH/throw_rethrow_test
TEST-FAIL: jit /SingleSource/Regression/C++/EH/throw_rethrow_test
TEST-FAIL: cbe /SingleSource/Regression/C++/EH/throw_rethrow_test
TEST-FAIL: llc /SingleSource/Regression/C++/BuiltinTypeInfo
TEST-FAIL: cbe /SingleSource/Regression/C++/BuiltinTypeInfo
TEST-FAIL: llc /SingleSource/Regression/C++/ofstream_ctor
TEST-FAIL: jit /SingleSource/Regression/C++/ofstream_ctor
TEST-FAIL: cbe /SingleSource/Regression/C++/ofstream_ctor
TEST-FAIL: llc /SingleSource/Benchmarks/Shootout-C++/except
TEST-FAIL: jit /SingleSource/Benchmarks/Shootout-C++/except
TEST-FAIL: cbe /SingleSource/Benchmarks/Shootout-C++/except
  * The above test fail because llvm-gcc4 doesn't support C++ EH

TEST-FAIL: llc /MultiSource/Applications/oggenc/oggenc
TEST-FAIL: jit /MultiSource/Applications/oggenc/oggenc
TEST-FAIL: cbe /MultiSource/Applications/oggenc/oggenc
  * Not sure, difference in binary output.

TEST-FAIL: jit /MultiSource/Applications/JM/ldecod/ldecod
  * Weird JIT problem, there's a PR filed on this.

TEST-FAIL: llc /MultiSource/Applications/JM/lencod/lencod
TEST-FAIL: jit /MultiSource/Applications/JM/lencod/lencod
TEST-FAIL: cbe /MultiSource/Applications/JM/lencod/lencod
  * Not sure, difference in numerical output

TEST-FAIL: jit /MultiSource/Applications/obsequi/Obsequi
  * Note sure.

TEST-FAIL: cbe /MultiSource/Benchmarks/Prolangs-C/archie-client/archie
  * Note sure, CBE failed to link:
    /tmp/cc5Bwjx8.o: In function `keepWaitingDirsend':
    archie.cbe.c:(.text+0x715): undefined reference to `ltmp_1856_85'
    archie.cbe.c:(.text+0x735): undefined reference to `ltmp_1857_86'
    /tmp/cc5Bwjx8.o: In function `retryDirsend':
    archie.cbe.c:(.text+0x8af): undefined reference to `ltmp_1856_85'
    archie.cbe.c:(.text+0x8cf): undefined reference to `ltmp_1857_86'
    /tmp/cc5Bwjx8.o: In function `archie_query':
    archie.cbe.c:(.text+0x1248): undefined reference to `ltmp_1141_82'

Reid.

On Thu, 2006-11-16 at 11:20 -0800, Reid Spencer wrote:
> Tanya,
> 
> 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?
>   * LLVM was built in Release mode in all cases
>   * I don't think this is ready for release. In particular the llvm-gcc4
> binary
>     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.
> 
> 
> BUILD LLVM WITH GCC 4.1.1 20060525 (FAIL)
>   * DwarfWriter.cpp:2400: warning: overflow in implicit constant
> conversion
>      Line looks like:    EmitInt32(DW_CIE_ID); EOL("CIE Identifier
> Tag");
>      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
> didn't bother
>   running the whole thing as it was clear that GCC 4.1.1 (still)
> mis-compiles LLVM.
> 
> 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)
> 
>   * PASS: make install, except these doc linkage errors:
>       /usr/bin/pod2html: llvm-nm.pod: cannot resolve L<ar(1)> in
> paragraph 51.
>       /usr/bin/pod2html: llvm-nm.pod: cannot resolve L<nm(1)> in
> paragraph 51.
>       /usr/bin/pod2html: llvm-ar.pod: cannot resolve L<ar(1)> in
> paragraph 114.
> 
>   * PASS: make check, except:
> 
> XPASS: /proj/llvm/rel1.9/llvm/test/Regression/CFrontend/2006-07-31-PR854.c
>       # of expected passes            1542
>       # of unexpected successes       1
>       # of expected failures          41
> 
> LLVM-TEST NIGHTLY WITH LLVM-GCC3 (FAIL)
>   * The following tests fail:
> TEST-FAIL: compile /SingleSource/UnitTests/2006-01-23-InitializedBitField
> TEST-FAIL: llc /SingleSource/UnitTests/2006-01-23-InitializedBitField
> TEST-FAIL: jit /SingleSource/UnitTests/2006-01-23-InitializedBitField
> TEST-FAIL: cbe /SingleSource/UnitTests/2006-01-23-InitializedBitField
> TEST-FAIL: compile /SingleSource/UnitTests/2006-01-23-UnionInit
> TEST-FAIL: llc /SingleSource/UnitTests/2006-01-23-UnionInit
> TEST-FAIL: jit /SingleSource/UnitTests/2006-01-23-UnionInit
> TEST-FAIL: cbe /SingleSource/UnitTests/2006-01-23-UnionInit
> TEST-FAIL: llc /SingleSource/Benchmarks/CoyoteBench/fftbench
> TEST-FAIL: jit /SingleSource/Benchmarks/CoyoteBench/fftbench
> TEST-FAIL: cbe /SingleSource/Benchmarks/CoyoteBench/fftbench
> TEST-FAIL: llc /SingleSource/Benchmarks/Shootout-C++/ackermann
> TEST-FAIL: jit /SingleSource/Benchmarks/Shootout-C++/ackermann
> TEST-FAIL: cbe /SingleSource/Benchmarks/Shootout-C++/ackermann
> TEST-FAIL: llc /SingleSource/Benchmarks/Shootout-C++/ary2
> TEST-FAIL: jit /SingleSource/Benchmarks/Shootout-C++/ary2
> TEST-FAIL: cbe /SingleSource/Benchmarks/Shootout-C++/ary2
> TEST-FAIL: llc /SingleSource/Benchmarks/Shootout-C++/ary3
> TEST-FAIL: jit /SingleSource/Benchmarks/Shootout-C++/ary3
> TEST-FAIL: cbe /SingleSource/Benchmarks/Shootout-C++/ary3
> TEST-FAIL: llc /SingleSource/Benchmarks/Shootout-C++/ary
> TEST-FAIL: jit /SingleSource/Benchmarks/Shootout-C++/ary
> TEST-FAIL: cbe /SingleSource/Benchmarks/Shootout-C++/ary
> TEST-FAIL: llc /SingleSource/Benchmarks/Shootout-C++/except
> TEST-FAIL: jit /SingleSource/Benchmarks/Shootout-C++/except
> TEST-FAIL: cbe /SingleSource/Benchmarks/Shootout-C++/except
> TEST-FAIL: llc /SingleSource/Benchmarks/Shootout-C++/fibo
> TEST-FAIL: jit /SingleSource/Benchmarks/Shootout-C++/fibo
> TEST-FAIL: cbe /SingleSource/Benchmarks/Shootout-C++/fibo
> TEST-FAIL: llc /SingleSource/Benchmarks/Shootout-C++/hash2
> TEST-FAIL: jit /SingleSource/Benchmarks/Shootout-C++/hash2
> TEST-FAIL: cbe /SingleSource/Benchmarks/Shootout-C++/hash2
> TEST-FAIL: llc /SingleSource/Benchmarks/Shootout-C++/hash
> TEST-FAIL: jit /SingleSource/Benchmarks/Shootout-C++/hash
> TEST-FAIL: cbe /SingleSource/Benchmarks/Shootout-C++/hash
> TEST-FAIL: llc /SingleSource/Benchmarks/Shootout-C++/hello
> TEST-FAIL: jit /SingleSource/Benchmarks/Shootout-C++/hello
> TEST-FAIL: cbe /SingleSource/Benchmarks/Shootout-C++/hello
> TEST-FAIL: llc /SingleSource/Benchmarks/Shootout-C++/lists1
> TEST-FAIL: jit /SingleSource/Benchmarks/Shootout-C++/lists1
> TEST-FAIL: cbe /SingleSource/Benchmarks/Shootout-C++/lists1
> TEST-FAIL: llc /SingleSource/Benchmarks/Shootout-C++/lists
> TEST-FAIL: jit /SingleSource/Benchmarks/Shootout-C++/lists
> TEST-FAIL: cbe /SingleSource/Benchmarks/Shootout-C++/lists
> TEST-FAIL: llc /SingleSource/Benchmarks/Shootout-C++/matrix
> TEST-FAIL: jit /SingleSource/Benchmarks/Shootout-C++/matrix
> TEST-FAIL: cbe /SingleSource/Benchmarks/Shootout-C++/matrix
> TEST-FAIL: llc /SingleSource/Benchmarks/Shootout-C++/methcall
> TEST-FAIL: jit /SingleSource/Benchmarks/Shootout-C++/methcall
> TEST-FAIL: cbe /SingleSource/Benchmarks/Shootout-C++/methcall
> TEST-FAIL: llc /SingleSource/Benchmarks/Shootout-C++/nestedloop
> TEST-FAIL: jit /SingleSource/Benchmarks/Shootout-C++/nestedloop
> TEST-FAIL: cbe /SingleSource/Benchmarks/Shootout-C++/nestedloop
> TEST-FAIL: llc /SingleSource/Benchmarks/Shootout-C++/objinst
> TEST-FAIL: jit /SingleSource/Benchmarks/Shootout-C++/objinst
> TEST-FAIL: cbe /SingleSource/Benchmarks/Shootout-C++/objinst
> TEST-FAIL: llc /SingleSource/Benchmarks/Shootout-C++/random
> TEST-FAIL: jit /SingleSource/Benchmarks/Shootout-C++/random
> TEST-FAIL: cbe /SingleSource/Benchmarks/Shootout-C++/random
> TEST-FAIL: jit /SingleSource/Benchmarks/Shootout-C++/reversefile
> TEST-FAIL: llc /SingleSource/Benchmarks/Shootout-C++/sieve
> TEST-FAIL: jit /SingleSource/Benchmarks/Shootout-C++/sieve
> TEST-FAIL: cbe /SingleSource/Benchmarks/Shootout-C++/sieve
> TEST-FAIL: jit /SingleSource/Benchmarks/Shootout-C++/spellcheck
> TEST-FAIL: llc /SingleSource/Benchmarks/Shootout-C++/strcat
> TEST-FAIL: jit /SingleSource/Benchmarks/Shootout-C++/strcat
> TEST-FAIL: cbe /SingleSource/Benchmarks/Shootout-C++/strcat
> TEST-FAIL: llc /SingleSource/Benchmarks/Shootout-C++/sumcol
> TEST-FAIL: jit /SingleSource/Benchmarks/Shootout-C++/sumcol
> TEST-FAIL: cbe /SingleSource/Benchmarks/Shootout-C++/sumcol
> TEST-FAIL: llc /SingleSource/Benchmarks/Shootout-C++/wc
> TEST-FAIL: jit /SingleSource/Benchmarks/Shootout-C++/wc
> TEST-FAIL: cbe /SingleSource/Benchmarks/Shootout-C++/wc
> TEST-FAIL: llc /SingleSource/Benchmarks/Misc-C++/bigfib
> TEST-FAIL: jit /SingleSource/Benchmarks/Misc-C++/bigfib
> TEST-FAIL: cbe /SingleSource/Benchmarks/Misc-C++/bigfib
> TEST-FAIL: llc /MultiSource/Applications/hexxagon/hexxagon
> TEST-FAIL: jit /MultiSource/Applications/hexxagon/hexxagon
> TEST-FAIL: cbe /MultiSource/Applications/hexxagon/hexxagon
> TEST-FAIL: llc /MultiSource/Applications/oggenc/oggenc
> TEST-FAIL: jit /MultiSource/Applications/oggenc/oggenc
> TEST-FAIL: cbe /MultiSource/Applications/oggenc/oggenc
> TEST-FAIL: jit /MultiSource/Applications/JM/ldecod/ldecod
> TEST-FAIL: llc /MultiSource/Applications/JM/lencod/lencod
> TEST-FAIL: jit /MultiSource/Applications/JM/lencod/lencod
> TEST-FAIL: cbe /MultiSource/Applications/JM/lencod/lencod
> TEST-FAIL: jit /MultiSource/Applications/obsequi/Obsequi
> TEST-FAIL: llc /MultiSource/Applications/kimwitu++/kc
> TEST-FAIL: jit /MultiSource/Applications/kimwitu++/kc
> TEST-FAIL: cbe /MultiSource/Applications/kimwitu++/kc
> TEST-FAIL: llc /MultiSource/Benchmarks/Prolangs-C++/city/city
> TEST-FAIL: jit /MultiSource/Benchmarks/Prolangs-C++/city/city
> TEST-FAIL: cbe /MultiSource/Benchmarks/Prolangs-C++/city/city
> TEST-FAIL: llc /MultiSource/Benchmarks/Prolangs-C++/deriv1/deriv1
> TEST-FAIL: jit /MultiSource/Benchmarks/Prolangs-C++/deriv1/deriv1
> TEST-FAIL: cbe /MultiSource/Benchmarks/Prolangs-C++/deriv1/deriv1
> TEST-FAIL: llc /MultiSource/Benchmarks/Prolangs-C++/deriv2/deriv2
> TEST-FAIL: jit /MultiSource/Benchmarks/Prolangs-C++/deriv2/deriv2
> TEST-FAIL: cbe /MultiSource/Benchmarks/Prolangs-C++/deriv2/deriv2
> TEST-FAIL: llc /MultiSource/Benchmarks/Prolangs-C++/employ/employ
> TEST-FAIL: jit /MultiSource/Benchmarks/Prolangs-C++/employ/employ
> TEST-FAIL: cbe /MultiSource/Benchmarks/Prolangs-C++/employ/employ
> TEST-FAIL: llc /MultiSource/Benchmarks/Prolangs-C++/garage/garage
> TEST-FAIL: jit /MultiSource/Benchmarks/Prolangs-C++/garage/garage
> TEST-FAIL: cbe /MultiSource/Benchmarks/Prolangs-C++/garage/garage
> TEST-FAIL: llc /MultiSource/Benchmarks/Prolangs-C++/office/office
> TEST-FAIL: jit /MultiSource/Benchmarks/Prolangs-C++/office/office
> TEST-FAIL: cbe /MultiSource/Benchmarks/Prolangs-C++/office/office
> TEST-FAIL: llc /MultiSource/Benchmarks/Prolangs-C++/shapes/shapes
> TEST-FAIL: jit /MultiSource/Benchmarks/Prolangs-C++/shapes/shapes
> TEST-FAIL: cbe /MultiSource/Benchmarks/Prolangs-C++/shapes/shapes
> 
> BUILD LLVM WITH LLVM-GCC4 CONFIGURED (PASS/FAIL)
>   * Configure failed to find llvm-gcc4 when the directory provided to
> --with-llvmgccdir
>     was the llvm-gcc4-1.9-x86-linux directory unpacked from the tarball.
> The 5-line
>     warning message at the end of configure run was produced. I don't
> know what configure
>     is looking for, but its not finding it.
>   * FAIL: 'make' failed in runtime library. Althought the runtime
> library isn't needed
>     with llvm-gcc4, it shouldn't fail to compile it:
>     make[3]: Entering directory
> `/proj/llvm/rel1.9/llvm/runtime/GCCLibraries/crtend'
>     llvm[3]: 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'
> 
> RUN LLVM-TEST WITH LLVM-GCC4 (FAIL)
>   * Most of the test (90%) fail compile with seg fault.
> 
> PATH="/proj/llvm/rel1.9/llvm/Release/bin:/proj/install/bin:/usr/lib/qt-3.3/bin:/usr/kerberos/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin:/home/reid/bin:/opt/j2sdk_1.4.2/j2sdk1.4.2/bin:/opt/oracle/bin" /proj/llvm/rel1.9/llvm-gcc4-1.9-x86-linux/bin/llvm-gcc -I/proj/llvm/rel1.9/llvm-test/SingleSource/UnitTests/Vector/SSE -I/proj/llvm/rel1.9/llvm-test/SingleSource/UnitTests/Vector/SSE -I/proj/llvm/rel1.9/llvm/include -I/proj/llvm/rel1.9/llvm-test/include -I../../../../include -I/proj/llvm/rel1.9/llvm/include -D_GNU_SOURCE -D__STDC_LIMIT_MACROS -D__NO_MATH_INLINES -O2 -msse2 -msse2 -O0 -S sse.expandfft.c -o Output/sse.expandfft.ll -emit-llvm
> sse.expandfft.c:268: internal compiler error: Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See <URL:http://llvm.org/bugs> for instructions.
> make[5]: [Output/sse.expandfft.ll] Error 1 (ignored)
> cp -f Output/sse.expandfft.ll Output/sse.expandfft.linked.rll
> cp: cannot stat `Output/sse.expandfft.ll': No such file or directory
> 
> 
> On Tue, 2006-11-14 at 09:49 -0800, Tanya M. Lattner wrote: 
> > LLVMers,
> > 
> > The LLVM 1.9 Prerelease is available for testing:
> > http://llvm.org/prereleases/1.9/
> > 
> > If anyone can spare some time, please download the appropriate tarballs 
> > for your platform and test the release (at least with make check). I'd 
> > also appreciate any documentation reviews.
> > 
> > Please note that llvm-gcc3 on x86 may not have a clean dejagnu run. You 
> > should see one XPASS for Regression/CFrontend/2006-07-31-PR854.c. If you 
> > are getting different failures or unexpected passes, please let me know. 
> > All other platforms should be clean.
> > 
> > If you find any problems, please email the list. I would appreciate this 
> > testing and documentation review to be completed by Friday, November 17th 
> > at 5:00PM PST.
> > 
> > If you plan to contribute llvm-gcc4 binaries for another platform, please 
> > complete them by the deadline above as well or send me an email with your 
> > status.
> > 
> > Thanks,
> > Tanya Lattner
> > _______________________________________________
> > LLVM Developers mailing list
> > LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
> 
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev

More information about the llvm-dev mailing list