Re: JIT compiling with LLVM v11 - Mailing list pgsql-hackers

From Andres Freund
Subject Re: JIT compiling with LLVM v11
Date
Msg-id 20180305050005.4wptjawnenk6jnjg@alap3.anarazel.de
Whole thread Raw
In response to Re: JIT compiling with LLVM v11  (Thomas Munro <thomas.munro@enterprisedb.com>)
Responses Re: JIT compiling with LLVM v11  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Hi,

On 2018-03-05 17:32:09 +1300, Thomas Munro wrote:
> I tried out your "jit" branch on my macOS 10.13.3 system.  Vendor "cc"
> and "c++" are version "Apple LLVM version 9.0.0 (clang-900.0.39.2)".
> I used MacPorts (whereas Peter E is using HomeBrew) to install LLVM
> with "sudo port install llvm-5.0".

Thanks for checking!


> warning: ignoring debug info with an invalid version (700000003) in
> /Users/munro/install/postgres/lib/llvmjit_types.bc

That's harmless, log output aside. Should strip the debug info there, to
remove the potential for that issue.


> Looking at llvm_get_function(), the function that raises that error, I
> see that there are a few different paths here.  I don't have
> HAVE_DECL_LLVMORCGETSYMBOLADDRESSIN defined, and I don't have LLVM <
> 5, so I should be getting the symbol address with
> LLVMOrcGetSymbolAddress(llvm_opt0_orc, &addr, mangled) or
> LLVMOrcGetSymbolAddress(llvm_opt3_orc, &addr, mangled), but clearly
> those are returning NULL.

Yep. I wonder if this is some symbol naming issue or such, because
emitting and relocating the object worked without an error.


> Not sure what's happening yet...

Hm. :/

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Incorrect use of "an" and "a" in code comments and docs
Next
From: Amit Langote
Date:
Subject: Re: ON CONFLICT DO UPDATE for partitioned tables