| From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: FYI: LLVM Runtime Crash |
| Date: | 2024-06-17 20:07:49 |
| Message-ID: | AD8D8A04-72CD-456E-9DD5-C0B2BA65FD5A@justatheory.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Jun 17, 2024, at 11:52, David E. Wheeler <david(at)justatheory(dot)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 into this 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 input LLVM IR. So this is likely a bug in the way postgres is generating LLVM IR: please file a bug against Postgres. (Feel free 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matthias van de Meent | 2024-06-17 20:25:09 | Re: [PATCH] Improve error message when trying to lock virtual tuple. |
| Previous Message | Robert Haas | 2024-06-17 19:39:27 | cost delay brainstorming |