| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Anthonin Bonnefoy <anthonin(dot)bonnefoy(at)datadoghq(dot)com> |
| Cc: | Andreas Karlsson <andreas(at)proxel(dot)se>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add missing JIT inline pass for llvm>=17 |
| Date: | 2026-01-20 19:03:45 |
| Message-ID: | zvm4e3i2bkqvlm2qrjmooitjqwbloxsqwnmauw3jggl6zr337n@lb2wyzownnkq |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2026-01-16 10:10:07 +0100, Anthonin Bonnefoy wrote:
> On Thu, Jan 15, 2026 at 2:51 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> > I'm strongly against removing the always inline pass, I see absolutely no
> > reason for doing that. The whole point of always inline is that it happens
> > unconditionally. It's not an expensive pass either.
>
> I've looked into more details on what was provided by 'default<O0>',
> and it turns out it includes an always-inline pass[0]. This is also
> visible when using debug-pass-manager:
Ah, that's good to know!
> So, with 'default<O0>,mem2reg', we replicate the same behaviour as
> pre-LLVM17 as it includes the always-inline pass.
>
> I've updated the patch to only add the inline pass when PGJIT_INLINE
> is on. I've also added a comment to mention that always-inline is
> included in O0.
That looks good to me.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Konstantin Knizhnik | 2026-01-20 19:04:39 | Mystery with REVOKE PRIVILEGE |
| Previous Message | Tom Lane | 2026-01-20 18:55:31 | Re: commented out code |