| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Latest LLVM breaks our code again |
| Date: | 2022-01-31 05:46:42 |
| Message-ID: | CA+hUKGKERyyX3s09CF73p83QD8CgkbD7cgJx2os1hE+jMWFmig@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jan 31, 2022 at 3:38 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Speaking of buildfarm breakage, seawasp has been failing for the
> past several days. It looks like bleeding-edge LLVM has again
> changed some APIs we depend on. First failure is here:
>
> https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=seawasp&dt=2022-01-28%2000%3A17%3A48
Oops, I missed this message. The patch at
https://www.postgresql.org/message-id/CA%2BhUKG%2BaGPBkBT5_4czkvzMu6-D%2BJgPaVL7mX_WBPXgGRndtXA%40mail.gmail.com
fixes the first two of these problems, and the third needs some more
work:
1. There's a missing #include <new> (must have been transitively
included before).
2. There's an API change that I'd written about already but hadn't
committed yet because seawasp is running behind my laptop at tracking
LLVM and I figured we might as well 'nagel' these kinds of commits.
3. We'll need to look into how to switch LLVMBuildCall -> LLVMBuildCall2 etc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Rouhaud | 2022-01-31 05:54:16 | Re: Is there a way (except from server logs) to know the kind of on-going/last checkpoint? |
| Previous Message | Thomas Munro | 2022-01-31 05:34:16 | Re: Spelling change in LLVM 14 API |