[llvm-testresults] OldGrawp-O0-PIC i386 nightly tester results

[Chris Lattner]

On Jan 15, 2008, at 9:57 PM, Apache wrote:
> http://llvm.org/nightlytest/test.php?machine=221&night=4582
> Name: il0102a-dhcp80.apple.com
> Nickname: OldGrawp-O0-PIC
> Buildstatus: OK
>
> New Test Failures:
> Benchmarks/MiBench/automotive-susan/automotive-susan [LLC compile, ]

Hi Evan,

Thanks for setting up the -O0 tester.  In the last couple of runs I've  
seen this failure and these as well:

New Test Failures:
Applications/JM/lencod/lencod [LLC compile, LLC-BETA compile, JIT  
codegen, LLC, LLC-BETA, JIT]

New Test Failures:
Benchmarks/FreeBench/mason/mason [LLC compile, LLC-BETA compile, JIT  
codegen, LLC, LLC-BETA, JIT]
Benchmarks/McCat/09-vor/vor [LLC compile, LLC-BETA compile, JIT  
codegen, LLC, LLC-BETA, JIT]
Benchmarks/Olden/bh/bh [LLC compile, LLC-BETA compile, JIT codegen,  
LLC, LLC-BETA, JIT]
Benchmarks/Olden/voronoi/voronoi [LLC compile, LLC-BETA compile, JIT  
codegen, LLC, LLC-BETA, JIT]
Benchmarks/Prolangs-C++/city/city [LLC compile, LLC-BETA compile, JIT  
codegen, LLC, LLC-BETA, JIT]
Benchmarks/Shootout-C++/moments [LLC compile, LLC-BETA compile, LLC,  
LLC-BETA]
Benchmarks/Shootout-C++/reversefile [LLC-BETA compile, LLC-BETA]
Regression/C++/EH/ConditionalExpr [LLC compile, LLC-BETA compile, LLC,  
LLC-BETA]
SPEC/CFP2006/447.dealII/447.dealII [LLC compile, LLC-BETA compile, JIT  
codegen, LLC, LLC-BETA, JIT]
SPEC/CINT2000/175.vpr/175.vpr [LLC compile, LLC-BETA compile, JIT  
codegen, LLC, LLC-BETA, JIT]
SPEC/CINT2006/458.sjeng/458.sjeng [LLC compile, LLC-BETA compile, JIT  
codegen, LLC, LLC-BETA, JIT]
SPEC/CINT2006/462.libquantum/462.libquantum [LLC compile, LLC-BETA  
compile, JIT codegen, LLC, LLC-BETA, JIT]
SPEC/CINT2006/473.astar/473.astar [JIT codegen, JIT]
UnitTests/2003-05-07-VarArgs [LLC compile, LLC-BETA compile, JIT  
codegen, LLC, LLC-BETA, JIT]
UnitTests/2003-08-11-VaListArg [LLC compile, LLC-BETA compile, JIT  
codegen, LLC, LLC-BETA, JIT]

Are these tests really failing at -O0 on x86-32?  If so, please file a  
bug, this should be a high priority for LLVM 2.2

Thanks,

-Chris