Re: [PATCH] jit: fix build with LLVM-21

From: Holger Hoffstätte <holger(at)applied-asynchrony(dot)com>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [PATCH] jit: fix build with LLVM-21
Date: 2025-10-10 11:10:35
Message-ID: 02bc1f96-a2c3-bbe9-091e-a5e4704f5151@applied-asynchrony.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2025-09-12 16:22, Holger Hoffstätte wrote:
> On 2025-09-12 14:47, Holger Hoffstätte wrote:
> <snip>
>> I temporarily removed the __arch64__ guard and can reproduce the above error,
>> using either gcc-15 or clang-21. It seems this llvm monkey patch backport thing
>> is affected by the following commit in llvm-21:
>> https://github.com/llvm/llvm-project/commit/cd585864c0bbbd74ed2a2b1ccc191eed4d1c8f90
>>
>> Trying to figure out how to adapt the code..
>
> Try the attached patch on your homebrew setup.
>
> This compiles and passes "make check", though I do not think it runs any jit tests.
> So intead I dropped this into my 17.6, disabled the __arch64__ guard to make sure
> I get the backport class, rebuilt and ran the jit on/off example from the docs.
> This showed the expected performance difference with jit=on vs. off.

Any news on the aarch64 front? The patch I sent in
https://www.postgresql.org/message-id/44718204-61a5-91b1-5574-154ff7a019f6%40applied-asynchrony.com

seemed to work for Anthonin Bonnefoy:
https://www.postgresql.org/message-id/CAO6_XqqbrO3O48f%2BXM0fp6P8ha61sZqYPuri%2B%2BP0%2BKMVM0xcdw%40mail.gmail.com

Just trying to make sure this doesn't fall into the couch crack.

thanks,
Holger

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alena Rybakina 2025-10-10 11:15:58 Re: pull-up subquery if JOIN-ON contains refs to upper-query
Previous Message Andrei Lepikhov 2025-10-10 11:05:04 Re: [PROPOSAL] Termination of Background Workers for ALTER/DROP DATABASE