[LLVMdev] [LLVMDev][3.5]: assertion failed in RuntimeDyldELF.cpp

[Lang Hames]

Hi Francis,

No worries. In that case, you may want to file a bug for this on
llvm.org/bugs. If you do that, it would be interesting to attach the stderr
output from the following command to the bug report:

/path-to-llvm-bin/lli -debug -use-mcjit -mtriple=x86_64-unknown-cygwin-elf
/cygdrive/z/dev/llvm/x64/llvm/test/ExecutionEngine/MCJIT/test-setcond-fp.ll

That will include some diagnostics from the runtime linker which may help
track down the cause of this issue.

Cheers,
Lang.



On Fri, Jul 25, 2014 at 12:21 AM, Francis ANDRE <
francis.andre.kampbell at orange.fr> wrote:

>  Hi Lang
>
>
> Le 24/07/2014 18:17, Lang Hames a écrit :
>
> Hi Francis,
>
>  It is possible to XFAIL a regression test (grep for XFAIL in the
> llvm/test directory for examples), however that's discouraged. The fact
> that this test is failing indicates that part of the JIT infrastructure is
> broken on W7/X86_64/Cygwin.
>
>  How long have you been building LLVM in this configuration? Do you know
> whether this is a recent regression?
>
> I am a newcomer on LLVM so I do not have any historical view on this
> issue.
>
> Francis
>
>
>  Cheers,
> Lang.
>
>
>
> On Tue, Jul 22, 2014 at 6:16 AM, Francis ANDRE <
> francis.andre.kampbell at orange.fr> wrote:
>
>> Hi LLVMDev list
>>
>> I am building LLVM from the SVN trunk at 213638 on a W7/X86_64/Cygwin
>> system and running make check leads to a series of failed assertions like
>>
>> ********************
>> FAIL: LLVM :: ExecutionEngine/MCJIT/test-setcond-fp.ll (6185 of 11245)
>> ******************** TEST 'LLVM ::
>> ExecutionEngine/MCJIT/test-setcond-fp.ll' FAILED ********************
>> Script:
>> --
>> /cygdrive/z/dev/llvm/x64/static/Release+Asserts/bin/lli -use-mcjit
>> -mtriple=x86_64-unknown-cygwin-elf
>> /cygdrive/z/dev/llvm/x64/llvm/test/ExecutionEngine/MCJIT/test-setcond-fp.ll
>> > /dev/null
>> --
>> Exit Code: 134
>>
>> Command Output (stderr):
>> --
>> assertion "RealOffset <= INT32_MAX && RealOffset >= INT32_MIN" failed:
>> file
>> "/cygdrive/z/dev/llvm/x64/llvm/lib/ExecutionEngine/RuntimeDyld/RuntimeDyldELF.cpp",
>> line 308, function: void
>> llvm::RuntimeDyldELF::resolveX86_64Relocation(const llvm::SectionEntry&,
>> uint64_t, uint64_t, uint32_t, int64_t, uint64_t)
>> Stack dump:
>> 0.      Program arguments:
>> /cygdrive/z/dev/llvm/x64/static/Release+Asserts/bin/lli -use-mcjit
>> -mtriple=x86_64-unknown-cygwin-elf
>> /cygdrive/z/dev/llvm/x64/llvm/test/ExecutionEngine/MCJIT/test-setcond-fp.ll
>> /cygdrive/z/dev/llvm/x64/static/test/ExecutionEngine/MCJIT/Output/test-setcond-fp.ll.script:
>> line 1:  5552 Aborted
>> /cygdrive/z/dev/llvm/x64/static/Release+Asserts/bin/lli -use-mcjit
>> -mtriple=x86_64-unknown-cygwin-elf
>> /cygdrive/z/dev/llvm/x64/llvm/test/ExecutionEngine/MCJIT/test-setcond-fp.ll
>> > /dev/null
>>
>> --
>>
>> How could I deal with the configuration of LLVM to avoid such assertion
>> error?
>>
>> FA
>> _______________________________________________
>> 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/20140725/53488386/attachment.html>