Re: [buildfarm related] Machines gcc experimental failed test_lfind

John Naylor <johncnaylorls@gmail.com>

From: John Naylor <johncnaylorls@gmail.com>
To: "Hayato Kuroda (Fujitsu)" <kuroda.hayato@fujitsu.com>
Cc: "pgsql-hackers@lists.postgresql.org" <pgsql-hackers@lists.postgresql.org>
Date: 2025-11-26T08:00:06Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Optimize vector8_has_le() on AArch64.

  2. Properly fix AVX-512 CRC calculation bug

On Wed, Nov 26, 2025 at 1:08 PM Hayato Kuroda (Fujitsu)
<kuroda.hayato@fujitsu.com> wrote:
> While seeing the buildfarm, I found that recently regression test for modules
> sometimes failed [1]. Typical example is [2] and failed at simd.h.
> The issue happened over branches, and they use gcc experimental. Based on that
> I felt recent commits for gcc might be related with.
>
> I don't have enough knowledge around here, but I saw commits in gcc and listed
> Candidates [4], [5], [6]. Can you find something from here?

We're not compiler engineers.

> Also, what should we do for nightly-built compilers? Will we fix tests or codes for them?

We might ask ourselves how often these have resulted in
forward-looking fixes for our code, weighed against spurious failures
and compiler bugs.

-- 
John Naylor
Amazon Web Services