Re: cannot to compile master in llvm_resolve_symbols

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: cannot to compile master in llvm_resolve_symbols
Date: 2022-09-22 10:59:11
Message-ID: CAFj8pRAZ9jBw7qhC0kfLu_=DWG6TkkQSsKNdtOee+Bu82zdo4g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

čt 22. 9. 2022 v 12:54 odesílatel Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
napsal:

> On Thu, Sep 22, 2022 at 10:43 PM Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
> wrote:
> > Today I found new bug
> >
> > -o llvmjit_wrap.o llvmjit_wrap.cpp -MMD -MP -MF .deps/llvmjit_wrap.Po
> > llvmjit.c: In function ‘llvm_resolve_symbols’:
> > llvmjit.c:1115:57: error: ‘LLVMJITCSymbolMapPair’ undeclared (first use
> in this function); did you mean ‘LLVMOrcCSymbolMapPair’?
> > 1115 | LLVMOrcCSymbolMapPairs symbols =
> palloc0(sizeof(LLVMJITCSymbolMapPair) * LookupSetSize);
> > |
> ^~~~~~~~~~~~~~~~~~~~~
> > |
> LLVMOrcCSymbolMapPair
>
> Hi Pavel,
>
> Some changes are needed for LLVM 15. I'm working on a patch, but it's
> not quite ready yet. Use LLVM 14 for now. There are a few
> superficial changes like that that are very easy to fix (that struct's
> name changed), but the real problem is that in LLVM 15 you have to do
> extra work to track the type of pointers and pass them into API calls
> that we have a lot of. https://llvm.org/docs/OpaquePointers.html

Thank you for info

Regards

Pavel

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message kuroda.hayato@fujitsu.com 2022-09-22 11:20:08 RE: Perform streaming logical transactions by background workers and parallel apply
Previous Message Thomas Munro 2022-09-22 10:54:00 Re: cannot to compile master in llvm_resolve_symbols