Re: pgsql: Track LLVM 15 changes.
От | Thomas Munro |
---|---|
Тема | Re: pgsql: Track LLVM 15 changes. |
Дата | |
Msg-id | CA+hUKG+p=faBQR2PSAqWoWa+_tJdKPT0wjZPQe7XcDEttUCgdQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pgsql: Track LLVM 15 changes. (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: pgsql: Track LLVM 15 changes.
Re: pgsql: Track LLVM 15 changes. |
Список | pgsql-committers |
On Wed, Feb 16, 2022 at 7:34 AM Tom Lane <tgl@sss.pgh.pa.us> wrote: > Although seawasp isn't actually failing at the moment, it's emitting > a boatload of deprecation warnings, eg > > In file included from llvmjit_deform.c:27: > ../../../../src/include/jit/llvmjit_emit.h:112:23: warning: 'LLVMBuildStructGEP' is deprecated: Use LLVMBuildStructGEP2instead to support opaque pointers [-Wdeprecated-declarations] > LLVMValueRef v_ptr = LLVMBuildStructGEP(b, v, idx, ""); > ^ > /home/fabien/clgtk/include/llvm-c/Core.h:3908:1: note: 'LLVMBuildStructGEP' has been explicitly marked deprecated here > LLVM_ATTRIBUTE_C_DEPRECATED( > ^ > > Is that on anyone's radar to clean up? Yeah I mentioned this problem in the other thread. I got as far as finding this write-up: https://llvm.org/docs/OpaquePointers.html I haven't yet tried to work out what we really need to do, but I'm planning to try. Possibly requires a bit more book keeping on our part, since eg LLVMGetElementType() is going away.
В списке pgsql-committers по дате отправления: