On Wed, Nov 8, 2023 at 4:46 AM Alvaro Herrera <alvhe...@alvh.no-ip.org> wrote:
> On 2023-Aug-25, Daniel Westermann (DWE) wrote:
> > I've just noticed this warning when building on Debian 12:
> >
> > In file included from
> > /usr/lib/llvm-14/include/llvm/Analysis/ModuleSummaryAnalysis.h:17,
> > from llvmjit_inline.cpp:51:
> > /usr/lib/llvm-14/include/llvm/IR/ModuleSummaryIndex.h: In constructor
> > ‘llvm::ModuleSummaryIndex::ModuleSummaryIndex(bool, bool)’:
> > /usr/lib/llvm-14/include/llvm/IR/ModuleSummaryIndex.h:1175:73: warning:
> > member ‘llvm::ModuleSummaryIndex::Alloc’ is used uninitialized
> > [-Wuninitialized]
> > 1175 | : HaveGVs(HaveGVs), EnableSplitLTOUnit(EnableSplitLTOUnit),
> > Saver(Alloc),
> > |
>
> Yeah, I get this one too. I thought commit 37d5babb5cfa ("jit: Support
> opaque pointers in LLVM 16.") was going to silence it, but I was quite
> mistaken. I gave that code a quick look and could not understand what
> it was complaining about. Is it a bug in the LLVM headers?
I found the commit where they fixed that in 15+:
https://github.com/llvm/llvm-project/commit/1d9086bf054c2e734940620d02d4451156b424e6
They don't seem to back-patch fixes, generally.
