Re: LLVM JIT: any JIT-compiled query crashes (SIGILL) on a libLLVM 19 + ASAN build

Hi Matheus,

> I think that the patches looks good and I also think that it's
> good to have a JIT test case since it's off by default. I'm just
> wondering if the the test patch should be 0003 instead 0001 since it
> will break CI if committed before the meson and autoconf changes.

Agreed on both counts. The series started out to show that the JIT
crash seen under Row Pattern Recognition was not RPR's fault but a
generic ASAN + JIT bitcode + debug-info problem, but since JIT is off
by default a dedicated test is worth having on its own, and I think it
makes a good seed to grow further coverage on.

And you're right about the ordering: if the test goes in first it turns
JIT on while the bitcode is still instrumented, so any commit between the
test and the build-system fixes would crash CI. I've reordered the
series so the fixes land first:

0001 meson: exclude sanitizer flags from the JIT bitcode.
(Author: Matheus Alcantara.)

0002 autoconf: same filtering for BITCODE_CFLAGS/CXXFLAGS, plus -g
under --enable-debug so the bitcode keeps its debug info.

0003 Add the "jit" regression test, which turns JIT on to push a
trivial query through the provider. This is the minimal case
that crashes the backend with ASAN enabled, and it passes again
once 0001/0002 are applied.

That way the build-system fixes precede the test at every point in the
history, so CI stays green wherever it is bisected.

Thanks!
Henson