|From:||Pierre Ducroquet <p(dot)psql(at)pinaraf(dot)info>|
|Cc:||Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers(at)postgresql(dot)org|
|Subject:||Re: JIT compiling with LLVM v10.0|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On Wednesday, February 7, 2018 3:54:05 PM CET Andres Freund wrote:
> I've pushed v10.0. The big (and pretty painful to make) change is that
> now all the LLVM specific code lives in src/backend/jit/llvm, which is
> built as a shared library which is loaded on demand.
> The layout is now as follows:
> Part of JITing always linked into the server. Supports loading the
> LLVM using JIT library.
> General code generation and optimization infrastructure
> llvmjit_error.cpp, llvmjit_wrap.cpp:
> Error / backward compat wrappers
> Cross module inlining support
> Expression compilation
> Deform compilation
> I generally like how this shaped out. There's a good amount of followup
> cleanup needed, but I'd appreciate some early feedback.
I also find it more readable and it looks cleaner, insane guys could be able
to write their own JIT engines for PostgreSQL by patching a single file :)
Since it's now in its own .so file, does it still make as much sense using
mostly the LLVM C API ?
I'll really look in the jit code itself later, right now I've just rebased my
previous patches and did a quick check that everything worked for LLVM4 and
I included a small addition to the gitignore file, I'm surprised you were not
bothered by the various .bc files generated.
Anyway, great work, and I look forward exploring the code :)
|Next Message||Robert Haas||2018-02-07 20:39:33||Re: postgres_fdw: perform UPDATE/DELETE .. RETURNING on a join directly|
|Previous Message||Stephen Frost||2018-02-07 18:42:54||Re: [HACKERS] Proposal: generic WAL compression|