Re: LLVM 22
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Devrim Gündüz <devrim@gunduz.org>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Matheus Alcantara <matheusssilv97@gmail.com>, Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>
Date: 2026-04-02T04:26:42Z
Lists: pgsql-hackers
Thomas Munro <thomas.munro@gmail.com> writes: > On Thu, Apr 2, 2026 at 4:31 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Just out of curiosity: I see you back-patched that all the way, >> but midge had only been failing on v18 and HEAD. Were you just >> being defensive, or is there something deeper there? > It was failing locally for me on all branches. Ah, thanks for that detail. > I don't know why midge wasn't failing on 14-17. Could jit be disabled > somewhere secret? Aarch64 vs amd64, but this issue doesn't seem to be > architecture related, it's IR-level. Definitely not arch-specific, because I reproduced it on x86_64. midge's lack of failure is odd then, but I'm not sure it's worth expending a lot of brain cells on. regards, tom lane
Commits
-
jit: No backport::SectionMemoryManager for LLVM 22.
- 9b354cfc5584 14.23 landed
- 963fccc09cc6 15.18 landed
- 8354cd7ff575 16.14 landed
- 0a2291b59f9b 17.10 landed
- 5c54e0f48fa2 18.4 landed
- be21341e13d9 19 (unreleased) landed
-
jit: Stop emitting lifetime.end for LLVM 22.
- b4e7cd428c00 14.23 landed
- c00ea2b5b4f1 15.18 landed
- 26f27c592c5d 16.14 landed
- b6d0cddbe27d 17.10 landed
- 78cea19bf7da 18.4 landed
- de6b80e5ff4b 19 (unreleased) landed