[cfe-dev] [LLVMdev] 2.6 pre-release2 ready for testing

Duncan Sands baldrick at free.fr
Tue Oct 20 06:02:12 PDT 2009


Hi Tanya,

> 1) Compile llvm from source and untar the llvm-test in the projects 
> directory (name it llvm-test or test-suite). Choose to use a 
> pre-compiled llvm-gcc or re-compile it yourself.

I compiled llvm and llvm-gcc with separate objects directories.
Platform is x86_64-linux-gnu.

> 2) Run make check, report any failures (FAIL or unexpected pass). Note 
> that you need to reconfigure llvm with llvm-gcc in your path or with 
> --with-llvmgccdir

One failure:

FAIL: llvm-2.6/llvm-2.6/test/Feature/load_module.ll for PR1318
Failed with exit(1) at line 1
while running:  llvm-as < llvm-2.6/llvm-2.6/test/Feature/load_module.ll 
|  opt -load=llvm-2.6/llvm-2.6-objects/Release/lib/LLVMHello.so -hello 
-disable-output - |& /bin/grep Hello
Error opening 'llvm-2.6-objects/Release/lib/LLVMHello.so': 
llvm-2.6-objects/Release/lib/LLVMHello.so: undefined symbol: _ZN4llvm4cerrE
child process exited abnormally

One unexpected pass:

XPASS: 
llvm-2.6/llvm-2.6/test/FrontendC/2009-08-11-AsmBlocksComplexJumpTarget.c

> 3) Run "make TEST=nightly report" and send me the report.nightly.txt

Attached.

Ciao,

Duncan.
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: report.nightly.txt
URL: <http://lists.llvm.org/pipermail/cfe-dev/attachments/20091020/20c8f18b/attachment.txt>


More information about the cfe-dev mailing list