> On 8 Dec 2023, at 14:38, Daniel Gustafsson wrote:
> I will apply that to v12 shortly after a little more testing.
Done, and canebrake/urutu has since turned green.
--
Daniel Gustafsson
> On 20 Nov 2023, at 22:53, Daniel Gustafsson wrote:
>
>> On 19 Nov 2023, at 21:08, Daniel Gustafsson wrote:
>
>> I'll have a look with fresh eyes in the morning, and hopefully it will be
>> fixable. If it get's messy it's quite possible that skipping v12 is the best
>> option.
>
> As an upda
> On 19 Nov 2023, at 21:08, Daniel Gustafsson wrote:
> I'll have a look with fresh eyes in the morning, and hopefully it will be
> fixable. If it get's messy it's quite possible that skipping v12 is the best
> option.
As an update, discussing with Andres off-list I have a potential patch for
th
> On 19 Nov 2023, at 17:05, Tom Lane wrote:
>
> Daniel Gustafsson writes:
>> llvmjit: Use explicit LLVMContextRef for inlining
>
> It looks like the v12 back-port of this wasn't quite right:
> canebrake and urutu have both been showing assertion failures
> down inside LLVMContextDispose since i
Daniel Gustafsson writes:
> llvmjit: Use explicit LLVMContextRef for inlining
It looks like the v12 back-port of this wasn't quite right:
canebrake and urutu have both been showing assertion failures
down inside LLVMContextDispose since it went in. They aren't
complaining about v13 and later, th
llvmjit: Use explicit LLVMContextRef for inlining
When performing inlining LLVM unfortunately "leaks" types (the
types survive and are usable, but a new round of inlining will
recreate new structurally equivalent types). This accumulation
will over time amount to a memory leak which for some queri
llvmjit: Use explicit LLVMContextRef for inlining
When performing inlining LLVM unfortunately "leaks" types (the
types survive and are usable, but a new round of inlining will
recreate new structurally equivalent types). This accumulation
will over time amount to a memory leak which for some queri
llvmjit: Use explicit LLVMContextRef for inlining
When performing inlining LLVM unfortunately "leaks" types (the
types survive and are usable, but a new round of inlining will
recreate new structurally equivalent types). This accumulation
will over time amount to a memory leak which for some queri
llvmjit: Use explicit LLVMContextRef for inlining
When performing inlining LLVM unfortunately "leaks" types (the
types survive and are usable, but a new round of inlining will
recreate new structurally equivalent types). This accumulation
will over time amount to a memory leak which for some queri
llvmjit: Use explicit LLVMContextRef for inlining
When performing inlining LLVM unfortunately "leaks" types (the
types survive and are usable, but a new round of inlining will
recreate new structurally equivalent types). This accumulation
will over time amount to a memory leak which for some queri
llvmjit: Use explicit LLVMContextRef for inlining
When performing inlining LLVM unfortunately "leaks" types (the
types survive and are usable, but a new round of inlining will
recreate new structurally equivalent types). This accumulation
will over time amount to a memory leak which for some queri
11 matches
Mail list logo
