[LLVMdev] [cfe-dev] ARM failures

[Dmitri Gribenko]

On Tue, Jan 8, 2013 at 8:31 PM, David Tweed <David.Tweed at arm.com> wrote:
> The obvious difference is that you're using --enable-optimized and implicitly --disable-assertions. If you run the tests with
>
> make check-all VERBOSE=1 'LIT_ARGS=-v ' > logfile
>
> and grep for FAILED in logfile, does what's listed there give any more details? (Quite possible in a Release-Asserts build
> it might not.)

All these tests fail with 'illegal instruction' signal.  For example:

******************** TEST 'LLVM ::
ExecutionEngine/MCJIT/2003-01-04-ArgumentBug.ll' FAILED
********************
Script:
--
/home/grib/clang/llvm-build-armhf/Release+Asserts/bin/lli
-mtriple=armv7l-unknown-linux-gnueabihf -use-mcjit
/home/grib/clang/llvm/test/ExecutionEngine/MCJIT/2003-01-04-ArgumentBug.ll
> /dev/null
--
Exit Code: 132
Command Output (stderr):
--
Stack dump:
0.      Program arguments:
/home/grib/clang/llvm-build-armhf/Release+Asserts/bin/lli
-mtriple=armv7l-unknown-linux-gnueabihf -use-mcjit
/home/grib/clang/llvm/test/ExecutionEngine/MCJIT/2003-01-04-ArgumentBug.ll
/home/grib/clang/llvm-build-armhf/test/ExecutionEngine/MCJIT/Output/2003-01-04-ArgumentBug.ll.script:
line 1: 28126 Illegal instruction
/home/grib/clang/llvm-build-armhf/Release+Asserts/bin/lli
-mtriple=armv7l-unknown-linux-gnueabihf -use-mcjit
/home/grib/clang/llvm/test/ExecutionEngine/MCJIT/2003-01-04-ArgumentBug.ll
> /dev/null

Dmitri

-- 
main(i,j){for(i=2;;i++){for(j=2;j<i;j++){if(!(i%j)){j=0;break;}}if
(j){printf("%d\n",i);}}} /*Dmitri Gribenko <gribozavr at gmail.com>*/