[LLVMdev] [cfe-dev] ARM failures

Galina Kistanova gkistanova at gmail.com
Tue Jan 8 12:50:59 PST 2013


Hello guys,

First of all, this builder is configured to send e-mails to the blame list.
I'm the owner of these 2 identical build slaves (which is listed in the
builder's properties :) ).
I keep an eye on this builder. Though, since builds take ~3 hours they
combine quite a lot of changes and the blame lists are long, it takes time
for people to notice and fix issues.

We do need more hardware, indeed.

The build has broken yesterday, then it has been fixed, and broken again.
If I get it right, the revisions in questions for the last break are
r171734 and r171735.

Let me know if anyone needs an access to one of the build slaves to debug.

And it is great that you care!

Thanks

Galina



On Tue, Jan 8, 2013 at 11:17 AM, Renato Golin <renato.golin at linaro.org>wrote:

> You can compare your configure/build arguments + environment with the
> build bot:
>
>
> http://lab.llvm.org:8011/builders/clang-native-arm-cortex-a9/builds/4313/steps/configure/logs/stdio
>
> I'll check how I built my LLVM on Chromebook tomorrow, but it didn't look
> too different to yours.
>
> --renato
>
>
> On 8 January 2013 19:08, Dmitri Gribenko <gribozavr at gmail.com> wrote:
>
>> 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>*/
>>
>
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130108/d4327319/attachment.html>


More information about the llvm-dev mailing list