Hi,
On Wed, 12 Mar 2025 at 16:39, Diego Fronza wrote:
>
> Hi,
>
> The v7 patch looks good to me, handling the bitcode modules in a uniform way
> and also avoiding the hacky code and warnings, much better now.
>
> A small note about the bitcode emission for generated sources in contrib,
> using
Hi,
The v7 patch looks good to me, handling the bitcode modules in a uniform
way and also avoiding the hacky code and warnings, much better now.
A small note about the bitcode emission for generated sources in contrib,
using cube as example, currently it creates two dict entries in a list:
bc_seg
Hi,
On Tue, 11 Mar 2025 at 01:04, Diego Fronza wrote:
> I did a full review on the provided patches plus some tests, I was able to
> validate that the loading of bitcode modules is working also JIT works for
> both backend and contrib modules.
Thank you!
> To test JIT on contrib modules I jus
Hello,
I did a full review on the provided patches plus some tests, I was able to
validate that the loading of bitcode modules is working also JIT works for
both backend and contrib modules.
To test JIT on contrib modules I just lowered the costs for all jit
settings and used the intarray extensi
Hi,
On Thu, 5 Sept 2024 at 12:24, Nazir Bilal Yavuz wrote:
>
> I found that Andres shared a patch
> (v17-0021-meson-Add-LLVM-bitcode-emission.patch) a while ago [1].
Andres and I continued to work on that. I think the patches are in
sharable state now and I wanted to hear opinions before proceed
Hi,
On Thu, 5 Sept 2024 at 11:56, Peter Eisentraut wrote:
>
> The meson build currently does not produce llvm bitcode (.bc) files.
> AFAIK, this is the last major regression for using meson for production
> builds.
>
> Is anyone working on that? I vaguely recall that some in-progress code
> was
