From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Anthonin Bonnefoy <anthonin(dot)bonnefoy(at)datadoghq(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Segfault in jit tuple deforming on arm64 due to LLVM issue |
Date: | 2024-10-17 09:41:05 |
Message-ID: | CA+hUKGL-DxDV047zZWZ2yEiFxe91Edv+JT7=Z6FUOts0N7OZ+A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Oct 17, 2024 at 10:36 PM Anthonin Bonnefoy
<anthonin(dot)bonnefoy(at)datadoghq(dot)com> wrote:
> I've run some additional tests, mostly pgbench with
> options=-cjit_above_cost=0 for an extended duration on an instance
> that was impacted. I haven't seen any issues nor performance
> regressions compared to the unpatched version.
>
> I will switch the commitfest entry to Ready for Committer if there's
> no objection.
Thanks! I'm going to go ahead and commit this. I asked Andres if he
wanted to object to this plan (as author of our LLVM stuff) and he did
not. I tried, for several frustrating days, to figure out how to
solve our problem using JITLink and stay on a more "supported" path,
but it all seems a bit unready, as various things don't work or aren't
available in various versions in our support range. At least I now
have the bones of a patch to prepare for JITLink in LLVM 20 or
whenever they force our hand... I'll write about that in a new thread
soon.
From | Date | Subject | |
---|---|---|---|
Next Message | Andrei Lepikhov | 2024-10-17 09:41:15 | Re: type cache cleanup improvements |
Previous Message | Anthonin Bonnefoy | 2024-10-17 09:35:57 | Re: Segfault in jit tuple deforming on arm64 due to LLVM issue |