Re: JIT compiling with LLVM v12.2 - Mailing list pgsql-hackers

On 2018-03-21 23:10:27 +1300, Thomas Munro wrote:
> On Wed, Mar 21, 2018 at 8:06 PM, Thomas Munro
> <thomas.munro@enterprisedb.com> wrote:
> > On Wed, Mar 21, 2018 at 4:07 PM, Andres Freund <andres@anarazel.de> wrote:
> >> Indeed. I've pushed a rebased version now, that basically just fixes the
> >> issue Thomas observed.
> >
> > I set up a 32 bit i386 virtual machine and installed Debian 9.4.
> 
> Next up, I have an arm64 system running Debian 9.4.  It bombs in
> "make check" and in simple tests:

Hum. Is it running a 32bit or 64 bit kernel/os?



> Program received signal SIGABRT, Aborted.
> __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
> 51      ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
> (gdb) bt
> #0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
> #1  0x0000ffff8f65adf4 in __GI_abort () at abort.c:89
> #2  0x0000ffff83e2de40 in __gnu_cxx::__verbose_terminate_handler() ()
> from /usr/lib/aarch64-linux-gnu/libstdc++.so.6
> #3  0x0000ffff83e2bd4c in ?? () from /usr/lib/aarch64-linux-gnu/libstdc++.so.6
> #4  0x0000ffff83e2bd98 in std::terminate() () from
> /usr/lib/aarch64-linux-gnu/libstdc++.so.6
> #5  0x0000ffff83e2c01c in __cxa_throw () from
> /usr/lib/aarch64-linux-gnu/libstdc++.so.6
> #6  0x0000ffff83e544bc in std::__throw_bad_function_call() () from
> /usr/lib/aarch64-linux-gnu/libstdc++.so.6
> #7  0x0000ffff85176a2c in LLVMOrcCreateInstance () from
> /usr/lib/aarch64-linux-gnu/libLLVM-3.9.so.1
> #8  0x0000ffff865c4db0 in llvm_session_initialize () at llvmjit.c:643
> #9  llvm_create_context (jitFlags=9) at llvmjit.c:136
> #10 0x0000ffff865cf8c8 in llvm_compile_expr (state=0xaaaaf2300208) at
> llvmjit_expr.c:132

Hm.


> With LLVM 5.0 (from backports) it seemed to get further (?):
> 
> Program terminated with signal SIGABRT, Aborted.
> #0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
> 51      ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
> (gdb) bt
> #0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:51
> #1  0x0000ffffa9642df4 in __GI_abort () at abort.c:89
> #2  0x0000ffff9d306e40 in __gnu_cxx::__verbose_terminate_handler() ()
> from /usr/lib/aarch64-linux-gnu/libstdc++.so.6
> #3  0x0000ffff9d304d4c in ?? () from /usr/lib/aarch64-linux-gnu/libstdc++.so.6
> #4  0x0000ffff9d304d98 in std::terminate() () from
> /usr/lib/aarch64-linux-gnu/libstdc++.so.6
> #5  0x0000ffff9d30501c in __cxa_throw () from
> /usr/lib/aarch64-linux-gnu/libstdc++.so.6
> #6  0x0000ffff9d32d4bc in std::__throw_bad_function_call() () from
> /usr/lib/aarch64-linux-gnu/libstdc++.so.6
> #7  0x0000ffff9eac7dc4 in ?? () from /usr/lib/aarch64-linux-gnu/libLLVM-5.0.so.1
> #8  0x0000aaaadd2dced0 in ?? ()
> #9  0x0000000040100401 in ?? ()
> Backtrace stopped: previous frame identical to this frame (corrupt stack?)
> (gdb)
> 
> Configure was run like this:
> 
> ./configure \
>   --prefix=$HOME/install \
>   --enable-cassert \
>   --enable-debug \
>   --with-llvm \
>   CC="ccache gcc" \
>   CXX="ccache g++" \
>   CLANG="ccache /usr/lib/llvm-3.9/bin/clang" \
>   LLVM_CONFIG="/usr/lib/llvm-3.9/bin/llvm-config"

I guess you'd swapped out 3.9 for 5.0?


> I can provide access to this thing if you think that'd be useful.

Perhaps that's necessary. Before that though, could you check how the
backtrace looks with LLVM debug symbols installed?

Greetings,

Andres Freund