Re: FYI: LLVM Runtime Crash - Mailing list pgsql-hackers

From David E. Wheeler
Subject Re: FYI: LLVM Runtime Crash
Date
Msg-id AD8D8A04-72CD-456E-9DD5-C0B2BA65FD5A@justatheory.com
Whole thread Raw
In response to FYI: LLVM Runtime Crash  ("David E. Wheeler" <david@justatheory.com>)
Responses Re: FYI: LLVM Runtime Crash
List pgsql-hackers
On Jun 17, 2024, at 11:52, David E. Wheeler <david@justatheory.com> wrote:

> I don’t *think* it’s something that can be fixed in Postgres core. This is mostly in FYI in case anyone else runs
intothis issue or knows something more about it. 

Okay, a response to the issue[1] says the bug is in Postgres:

> The error message is LLVM reporting the backend can't handle the particular form of "probe-stack" attribute in the
inputLLVM IR. So this is likely a bug in the way postgres is generating LLVM IR: please file a bug against Postgres.
(Feelfree to reopen if you have some reason to believe the issue is on the LLVM side.) 

Would it be best for me to send a report to pgsql-bugs?

Best,

David

[1]: https://github.com/llvm/llvm-project/issues/95804#issuecomment-2174310977




pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: cost delay brainstorming
Next
From: Matthias van de Meent
Date:
Subject: Re: [PATCH] Improve error message when trying to lock virtual tuple.