Re: FYI: LLVM Runtime Crash

From: Andres Freund <andres(at)anarazel(dot)de>
To: "David E(dot) Wheeler" <david(at)justatheory(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: FYI: LLVM Runtime Crash
Date: 2024-06-17 20:37:21
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


On 2024-06-17 16:07:49 -0400, David E. Wheeler wrote:
> 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.)

I suspect the issue might be that the version of clang and LLVM are diverging
too far. Does it work if you pass CLANG=/opt/homebrew/opt/llvm/bin/clang to


Andres Freund

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message David E. Wheeler 2024-06-17 20:48:29 Re: FYI: LLVM Runtime Crash
Previous Message Tom Lane 2024-06-17 20:37:05 Xact end leaves CurrentMemoryContext = TopMemoryContext