Re: BUG #16696: Backend crash in llvmjit - Mailing list pgsql-bugs

From Andres Freund
Subject Re: BUG #16696: Backend crash in llvmjit
Date
Msg-id 20210721165927.3x6cazq3hsni6m7r@alap3.anarazel.de
Whole thread Raw
In response to Re: BUG #16696: Backend crash in llvmjit  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: BUG #16696: Backend crash in llvmjit  (Thomas Munro <thomas.munro@gmail.com>)
List pgsql-bugs
Hi,

On 2021-07-18 17:13:50 +1200, Thomas Munro wrote:
> On Thu, May 20, 2021 at 2:49 AM Palle <girgen@pingpong.net> wrote:
> > This seems to still not be fixed. Is it planned for 14.0 release?
> 
> I don't know enough about LLVM and TLS to have an opinion on the
> details, but I tested this and it works, and I think it should
> probably be back-patched based on the discussion so far (and hopefully
> in the future some way can be figured out to make it actually work?).
> 
> When I tested the original repro, I got SIGTRAP (not SIGSEGV as
> reported) with LLVM 9 and 10, while 11, 12 and 13 failed gracefully
> with:
> 
> 2021-07-18 15:27:42.785 NZST [78884] FATAL:  fatal llvm error:
> Relocation type not implemented yet!
> 
> I was reminded of this thread because I happened to see a
> relevant-looking commit whiz past in the FreeBSD commit log[1]: libc
> is changing to a different TLS model.  I just tried that, and it makes
> no difference.

FWIW, there's ongoing work in llvm to make the jit stuff handle TLS
correctly.

Greetings,

Andres Freund



pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #17066: Cache lookup failed when null (iso-8859-1) is passed as anycompatiblemultirange
Next
From: PG Bug reporting form
Date:
Subject: BUG #17118: ALTER TABLE doesn't discard redundant UNIQUE constraints as CREATE TABLE will