Thomas Munro writes:
> there's also the walker stuff[1] to address.
Yeah. I just did some experimentation with that, and it looks like
neither gcc nor clang will cut you any slack at all for declaring
an argument as "void *": given say
typedef bool (*tree_walker_callback) (Node *node, void *con
On Sat, Sep 17, 2022 at 6:45 AM Andres Freund wrote:
> On 2022-09-16 11:40:46 -0400, Tom Lane wrote:
> > According to
> >
> > https://bugzilla.redhat.com/show_bug.cgi?id=2127503
> >
> > bleeding-edge clang complains thusly:
> >
> > llvmjit_inline.cpp: In function 'std::unique_ptr
> > llvm_load_su
Hi,
On 2022-09-16 16:07:51 -0400, Tom Lane wrote:
> Andres Freund writes:
> > On 2022-09-16 11:40:46 -0400, Tom Lane wrote:
> >> I suspect this is less about clang and more about LLVM APIs,
> >> but anyway it seems like we gotta fix something.
>
> > Yea, there's definitely a bunch of llvm 15 issu
Andres Freund writes:
> On 2022-09-16 11:40:46 -0400, Tom Lane wrote:
>> I suspect this is less about clang and more about LLVM APIs,
>> but anyway it seems like we gotta fix something.
> Yea, there's definitely a bunch of llvm 15 issues that need to be fixed - this
> particular failure is pretty
Hi,
On 2022-09-16 11:40:46 -0400, Tom Lane wrote:
> According to
>
> https://bugzilla.redhat.com/show_bug.cgi?id=2127503
>
> bleeding-edge clang complains thusly:
>
> llvmjit_inline.cpp: In function 'std::unique_ptr
> llvm_load_summary(llvm::StringRef)':
> llvmjit_inline.cpp:771:37: error: in
According to
https://bugzilla.redhat.com/show_bug.cgi?id=2127503
bleeding-edge clang complains thusly:
llvmjit_inline.cpp: In function 'std::unique_ptr
llvm_load_summary(llvm::StringRef)':
llvmjit_inline.cpp:771:37: error: incomplete type 'llvm::MemoryBuffer' used in
nested name specifier
77
