| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | rekgrpth(at)gmail(dot)com, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17927: Postgres does not compile with LLVM-16 |
| Date: | 2023-05-10 13:09:55 |
| Message-ID: | 7AA0E02C-F7FB-4515-ACC5-306B791D2E61@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> On 10 May 2023, at 12:10, PG Bug reporting form <noreply(at)postgresql(dot)org> wrote:
Thanks for your report!
> llvmjit.c:506:24: warning: returning 'int' from a function with return type
> 'LLVMValueRef' {aka 'struct LLVMOpaqueValue *'} makes pointer from integer
> without a cast [-Wint-conversion]
> 506 | return LLVMBuildLoad(builder, v_fn, "");
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
This is a known problem which is currently being worked on. LLVM 16 deprecated
typed pointers which the postgres JIT implementation is using, switching over
to opaque pointers is no simple task though.
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2023-05-11 08:00:01 | BUG #17928: Standby fails to decode WAL on termination of primary |
| Previous Message | PG Bug reporting form | 2023-05-10 10:10:12 | BUG #17927: Postgres does not compile with LLVM-16 |