Re: LLVM 22
Thomas Munro <thomas.munro@gmail.com>
From: Thomas Munro <thomas.munro@gmail.com>
To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Cc: Matheus Alcantara <matheusssilv97@gmail.com>, Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>
Date: 2026-01-22T02:24:56Z
Lists: pgsql-hackers
On Sun, Jan 11, 2026 at 8:09 PM Thomas Munro <thomas.munro@gmail.com> wrote: > A new unrelated assertion started firing in LLVM main/22 a few days ago: > > v_nullbytemask = l_int8_const(lc, 1 << ((attnum) & 0x07)); > Assertion failed: (llvm::isUIntN(BitWidth, val) && "Value is not > an N-bit unsigned value") > > Here is a fix for that. 22 was branched and RC1 is out, but that particular change was reverted from 22[1]. It had already been through a commit/revert cycle before and at a wild guess, it probably caused too much work elsewhere with not enough notice. It's still present in main, so consider the v2-0003 patch booted out of here and into the not-yet-created LLVM 23 thread... [1] https://github.com/llvm/llvm-project/commit/16bf1c5d6b7f8fda16da5df5a2b195a6b10d08ed
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