[llvm-dev] EH failures in MCJIT
Eric Fiselier via llvm-dev
llvm-dev at lists.llvm.org
Sat Mar 5 23:38:41 PST 2016
I recognize these failures, and I think they should be fixed when building
with clang 3.8. IIRC the cause of the errors is that libc++abi.so linked to
the wrong unwinding libraries pre-3.8. I believe the relevant commit is
r255559 (http://reviews.llvm.org/rL255559).
PS. You should use -DLLVM_ENABLE_LIBCXX=ON instead of
-DCMAKE_CXX_FLAGS='-stdlib=libc++'.
/Eric
On Thu, Mar 3, 2016 at 7:39 AM, Krzysztof Parzyszek via llvm-dev <
llvm-dev at lists.llvm.org> wrote:
> Hi Lang,
>
> I am on Ubuntu 14.04.
> I am building ToT: llvm, clang, polly, lld, compiler-rt, libcxx, libcxxabi.
> The build compiler is: clang+llvm-3.7.0-x86_64-linux-gnu-ubuntu-14.04
> The failures show up during "make check-all".
>
> My cmake command was:
>
> cmake -G 'Unix Makefiles'
> -DCMAKE_BUILD_TYPE=Release
> -DCMAKE_INSTALL_PREFIX=/w/c/org
> -DLLVM_TARGETS_TO_BUILD:STRING=all
> -DLLVM_BUILD_RUNTIME:BOOL=ON
> -DLIBCLANG_BUILD_STATIC=ON
> -DLLVM_ENABLE_PIC:BOOL=ON
> -DLLVM_ENABLE_ASSERTIONS:BOOL=ON
> -DLLVM_INCLUDE_TOOLS:BOOL=ON
> -DLLVM_LIT_ARGS:STRING="-s -v"
> -DWITH_POLLY:BOOL=ON
> -DLINK_POLLY_INTO_TOOLS:BOOL=ON
>
>
> -DCMAKE_C_COMPILER=/w/c/clang+llvm-3.7.0-x86_64-linux-gnu-ubuntu-14.04/bin/clang
>
>
> -DCMAKE_CXX_COMPILER=/w/c/clang+llvm-3.7.0-x86_64-linux-gnu-ubuntu-14.04/bin/clang++
> -DCMAKE_CXX_FLAGS='-stdlib=libc++'
> -DCMAKE_BUILD_WITH_INSTALL_RPATH=1
>
>
> '-DCMAKE_INSTALL_RPATH:STRING=/w/c/clang+llvm-3.7.0-x86_64-linux-gnu-ubuntu-14.04/lib'
> -DCMAKE_EXE_LINKER_FLAGS='-lc++ -lc++abi'
> -DCMAKE_SHARED_LINKER_FLAGS='-lc++ -lc++abi'
> /w/src/llvm.org
>
> -Krzysztof
>
>
>
> On 3/2/2016 6:21 PM, Lang Hames wrote:
>
>> Hi Krzysztof,
>>
>> If I understand correctly you're building LLVM top-of-tree with 3.7.0?
>> Or is this a bug in 3.7.0?
>>
>> What operating system are you on?
>>
>> Cheers,
>> Lang.
>>
>>
>> On Wed, Mar 2, 2016 at 2:22 PM, Krzysztof Parzyszek via llvm-dev
>> <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote:
>>
>> After re-cmaking and rebuilding everything from scratch, I'm seeing
>> failures in MCJIT. It this something known or expected? I build
>> LLVM/clang with pre-packaged clang-3.7.0, with "-stdlib=libc++".
>>
>>
>> Example failure:
>>
>> /w/bld/org/./bin/lli -remote-mcjit
>> -mcjit-remote-process=/w/bld/org/./bin/lli-child-target
>> /w/src/llvm.org/test/ExecutionEngine/MCJIT/remote/eh.ll
>> <http://llvm.org/test/ExecutionEngine/MCJIT/remote/eh.ll>
>> --
>> Exit Code: 184
>>
>> Command Output (stderr):
>> --
>> warning: remote mcjit does not support lazy compilation
>> terminating with uncaught exception of type int
>> ERROR: Unexpected RPC call
>>
>> --
>>
>> ********************
>> FAIL: LLVM :: ExecutionEngine/MCJIT/eh.ll (18164 of 33466)
>> ******************** TEST 'LLVM :: ExecutionEngine/MCJIT/eh.ll'
>> FAILED ********************
>> Script:
>> --
>> /w/bld/org/./bin/lli
>> /w/src/llvm.org/test/ExecutionEngine/MCJIT/eh.ll
>> <http://llvm.org/test/ExecutionEngine/MCJIT/eh.ll>
>>
>> --
>> Exit Code: 134
>>
>> Command Output (stderr):
>> --
>> terminating with uncaught exception of type int
>> #0 0x0000000000b6ec28 llvm::sys::PrintStackTrace(llvm::raw_ostream&)
>> (/w/bld/org/bin/lli+0xb6ec28)
>> #1 0x0000000000b6d1e6 llvm::sys::RunSignalHandlers()
>> (/w/bld/org/bin/lli+0xb6d1e6)
>> #2 0x0000000000b6f25b SignalHandler(int) (/w/bld/org/bin/lli+0xb6f25b)
>> #3 0x00002b45866ce340 __restore_rt
>> (/lib/x86_64-linux-gnu/libpthread.so.0+0x10340)
>> #4 0x00002b4587047cc9 gsignal
>>
>> /build/buildd/eglibc-2.19/signal/../nptl/sysdeps/unix/sysv/linux/raise.c:56:0
>> #5 0x00002b458704b0d8 abort
>> /build/buildd/eglibc-2.19/stdlib/abort.c:91:0
>> #6 0x00002b4586068287
>>
>> (/w/c/clang+llvm-3.7.0-x86_64-linux-gnu-ubuntu-14.04/lib/libc++abi.so.1+0x8287)
>> #7 0x00002b4586068438
>>
>> (/w/c/clang+llvm-3.7.0-x86_64-linux-gnu-ubuntu-14.04/lib/libc++abi.so.1+0x8438)
>> #8 0x00002b45860a1da3 std::__terminate(void (*)())
>>
>> (/w/c/clang+llvm-3.7.0-x86_64-linux-gnu-ubuntu-14.04/lib/libc++abi.so.1+0x41da3)
>> #9 0x00002b45860a1536 __cxa_throw
>>
>> (/w/c/clang+llvm-3.7.0-x86_64-linux-gnu-ubuntu-14.04/lib/libc++abi.so.1+0x41536)
>> #10 0x00002b4585ba702d
>> #11 0x00002b4585ba703d
>> #12 0x00000000008ce7db llvm::MCJIT::runFunction(llvm::Function*,
>> llvm::ArrayRef<llvm::GenericValue>) (/w/bld/org/bin/lli+0x8ce7db)
>> #13 0x000000000086f3cd
>> llvm::ExecutionEngine::runFunctionAsMain(llvm::Function*,
>> std::__1::vector<std::__1::basic_string<char,
>> std::__1::char_traits<char>, std::__1::allocator<char> >,
>> std::__1::allocator<std::__1::basic_string<char,
>> std::__1::char_traits<char>, std::__1::allocator<char> > > > const&,
>> char const* const*) (/w/bld/org/bin/lli+0x86f3cd)
>> #14 0x000000000052cc13 main (/w/bld/org/bin/lli+0x52cc13)
>> #15 0x00002b4587032ec5 __libc_start_main
>> /build/buildd/eglibc-2.19/csu/libc-start.c:321:0
>> #16 0x0000000000528ec7 _start (/w/bld/org/bin/lli+0x528ec7)
>> Stack dump:
>> 0. Program arguments: /w/bld/org/./bin/lli
>> /w/src/llvm.org/test/ExecutionEngine/MCJIT/eh.ll
>> <http://llvm.org/test/ExecutionEngine/MCJIT/eh.ll>
>> /w/bld/org/test/ExecutionEngine/MCJIT/Output/eh.ll.script: line 1:
>> 420 Aborted (core dumped) /w/bld/org/./bin/lli
>> /w/src/llvm.org/test/ExecutionEngine/MCJIT/eh.ll
>> <http://llvm.org/test/ExecutionEngine/MCJIT/eh.ll>
>>
>>
>> There are 10 of them in total. They are all about "terminating with
>> uncaught exception of type int".
>>
>>
>> Failing Tests (10):
>> LLVM :: ExecutionEngine/MCJIT/eh-lg-pic.ll
>> LLVM :: ExecutionEngine/MCJIT/eh-sm-pic.ll
>> LLVM :: ExecutionEngine/MCJIT/eh.ll
>> LLVM :: ExecutionEngine/MCJIT/multi-module-eh-a.ll
>> LLVM :: ExecutionEngine/MCJIT/remote/eh.ll
>> LLVM :: ExecutionEngine/OrcMCJIT/eh-lg-pic.ll
>> LLVM :: ExecutionEngine/OrcMCJIT/eh-sm-pic.ll
>> LLVM :: ExecutionEngine/OrcMCJIT/eh.ll
>> LLVM :: ExecutionEngine/OrcMCJIT/multi-module-eh-a.ll
>> LLVM :: ExecutionEngine/OrcMCJIT/remote/eh.ll
>>
>>
>> -Krzysztof
>>
>>
>> --
>> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
>> hosted by The Linux Foundation
>> _______________________________________________
>> LLVM Developers mailing list
>> llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>
>> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>>
>>
>>
>
> --
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted
> by The Linux Foundation
> _______________________________________________
> LLVM Developers mailing list
> llvm-dev at lists.llvm.org
> http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20160306/718537de/attachment.html>
More information about the llvm-dev
mailing list