Re: Add missing JIT inline pass for llvm>=17 - Mailing list pgsql-hackers

From Andreas Karlsson
Subject Re: Add missing JIT inline pass for llvm>=17
Date
Msg-id a60e000e-7ebb-4ab5-9fff-73c0491d1154@proxel.se
Whole thread Raw
In response to Add missing JIT inline pass for llvm>=17  (Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>)
Responses Re: Add missing JIT inline pass for llvm>=17
Re: Add missing JIT inline pass for llvm>=17
List pgsql-hackers
Great find! Sadly shows how little people actually use JIT.

On 1/14/26 9:02 AM, Anthonin Bonnefoy wrote:
> I didn't add the always-inline pass as I don't think this can have any
> effect. From what I understand, the functions need to be imported
> through llvm_inline for LLVM to be able to inline them. I've tested by
> tagging int4mod as always inline, and the generated bc was still
> calling the function despite the always-inline pass.

If inline-always does not do anything it should be removed on older LLVM 
versions too. I do not think we should be having pre- and post-LLVM 17 
run different passes. But as Thomas pointed out inline-always is likely 
used for tuple deforming.

Andreas




pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Add missing JIT inline pass for llvm>=17
Next
From: jian he
Date:
Subject: Re: Enable partitionwise join for partition keys wrapped by RelabelType