[LLVMdev] LLVM on ARM testing.

[James Molloy]

Hi,

Most of those test failures are due to the JIT, which is unmaintained for
ARM and known to be dead. The only ones that worry me are the objdump ones,
but llvm-objdump is still under development so it's not so surprising.

Cheers,

James

-----Original Message-----
From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On
Behalf Of Siarhei Siamashka
Sent: 29 November 2011 08:40
To: Karel Gardas
Cc: llvmdev at cs.uiuc.edu
Subject: Re: [LLVMdev] LLVM on ARM testing.

On Sun, Jul 3, 2011 at 11:32 PM, Karel Gardas <karel.gardas at centrum.cz>
wrote:
> Hello,
>
> I asked here for kind of reference GCC version which LLVM development
> team is using for *native* testing on ARM hardware. (no cross
> compilation!) last week or so. I've been curious myself how the
> situation looks and so I tested LLVM 2.9 as a reference point and LLVM
> HEAD as of June 29 on ARMv7 (two boards with two different Ubuntu
> versions) compiled by GCC 4.3.4, 4.4.1, 4.4.5, 4.5.2, 4.6.1 Linaro
> 2011.05 and 4.6.1 Linaro 2011.06. It looks like LLVM HEAD does have
> about 28 regressions in comparison with LLVM 2.9. If you are curious to
> know more or to get actual `make check' logs for all the combinations
> please see http://ghcarm.wordpress.com/2011/07/03/llvm-on-arm-testing/
>
> Is there anything other I might do for you to get those regressions fixed?

I'm curious if anybody is still tracking the status of ARM support in
LLVM. Right now I'm getting the following errors for llvm-3.0rc4 test
suite on arm linux system:

********************
Testing Time: 2136.45s
********************
Failing Tests (7):
    LLVM :: ExecutionEngine/2002-12-16-ArgTest.ll
    LLVM :: ExecutionEngine/test-fp.ll
    LLVM :: Object/objdump-disassembly-inline-relocations.test
    LLVM :: Object/objdump-trivial-object.test
    LLVM-Unit :: ExecutionEngine/JIT/Release/JITTests/JIT.GlobalInFunction
    LLVM-Unit ::
ExecutionEngine/JIT/Release/JITTests/JITTest.AvailableExternallyGlobalIsntEm
itted
    LLVM-Unit ::
ExecutionEngine/JIT/Release/JITTests/JITTest.FunctionPointersOutliveTheirCre
ator

  Expected Passes    : 3239
  Expected Failures  : 46
  Unsupported Tests  : 2352
  Unexpected Failures: 7

$ gcc -v
Using built-in specs.
COLLECT_GCC=/usr/armv7a-unknown-linux-gnueabi/gcc-bin/4.5.3/gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/armv7a-unknown-linux-gnueabi/4.5.3/lto-
wrapper
Target: armv7a-unknown-linux-gnueabi
Configured with:
/var/tmp/portage/sys-devel/gcc-4.5.3-r1/work/gcc-4.5.3/configure
--prefix=/usr --bindir=/usr/armv7a-unknown-linux-gnueabi/gcc-bin/4.5.3
--includedir=/usr/lib/gcc/armv7a-unknown-linux-gnueabi/4.5.3/include
--datadir=/usr/share/gcc-data/armv7a-unknown-linux-gnueabi/4.5.3
--mandir=/usr/share/gcc-data/armv7a-unknown-linux-gnueabi/4.5.3/man
--infodir=/usr/share/gcc-data/armv7a-unknown-linux-gnueabi/4.5.3/info
--with-gxx-include-dir=/usr/lib/gcc/armv7a-unknown-linux-gnueabi/4.5.3/inclu
de/g++-v4
--host=armv7a-unknown-linux-gnueabi
--build=armv7a-unknown-linux-gnueabi --disable-altivec
--disable-fixed-point --without-ppl --without-cloog --disable-lto
--enable-nls --without-included-gettext --with-system-zlib
--disable-werror --enable-secureplt --disable-multilib
--enable-libmudflap --disable-libssp --enable-libgomp
--with-python-dir=/share/gcc-data/armv7a-unknown-linux-gnueabi/4.5.3/python
--enable-checking=release --disable-libgcj --with-arch=armv7-a
--enable-languages=c,c++,fortran --enable-shared
--enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu
--with-bugurl=http://bugs.gentoo.org/ --with-pkgversion='Gentoo
4.5.3-r1 p1.0, pie-0.4.5'
Thread model: posix
gcc version 4.5.3 (Gentoo 4.5.3-r1 p1.0, pie-0.4.5)

And the failures are the same if using gcc 4.4.5 instead.

-- 
Best regards,
Siarhei Siamashka
_______________________________________________
LLVM Developers mailing list
LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev