Re: BUG #16516: when testing jit get terminate called after throwing an instance of 'std::bad_function_call'

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: reiner(dot)peterke(at)splendiddata(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16516: when testing jit get terminate called after throwing an instance of 'std::bad_function_call'
Date: 2020-06-30 04:35:51
Message-ID: CA+hUKGKxuj3JzEa3X_UOF8QGVtFUEOgLiMHJHLfkNdz3mEwi0w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Jun 29, 2020 at 9:19 PM PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 16516
> Logged by: reiner peterke
> Email address: reiner(dot)peterke(at)splendiddata(dot)com
> PostgreSQL version: 12.3
> Operating system: Centos 7.8.2003, redhat 7.8, sles 12 sp5
> Description:
>
> Testing jit functionality power8 architecture

> terminate called after throwing an instance of 'std::bad_function_call'

Hi, I think this was a problem with LLVM on POWER with LLVM versions
before 7. There have been a couple of discussions of it in the mail
archives, and the problem was on the LLVM side, fixed in later
releases. I suspect you either need to somehow get a build with newer
LLVM, or you need to disable jit.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Pavel Biryukov 2020-06-30 07:09:13 Re: posgres 12 bug (partitioned table)
Previous Message Hamid Akhtar 2020-06-30 04:28:43 Re: BUG #16516: when testing jit get terminate called after throwing an instance of 'std::bad_function_call'