Horton
Menu

Re: Build failure with GCC 15 (defaults to -std=gnu23)

Robins Tharakan <tharakan@gmail.com>

View thread
From: Robins Tharakan <tharakan@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andres Freund <andres@anarazel.de>, Thomas Munro <thomas.munro@gmail.com>, Peter Eisentraut <peter@eisentraut.org>, Sam James <sam@gentoo.org>, pgsql-bugs@lists.postgresql.org
Date: 2024-12-07T11:42:07Z
Lists: pgsql-bugs 
On Sat, 30 Nov 2024 at 02:02, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Robins Tharakan <tharakan@gmail.com> writes:
> > alligator/HEAD is still failing though.
> > Let me know if changing something on alligator can help in some way.
>
> I think we're waiting on the gcc crew to fix their bug.  As long
> as alligator is faithfully rebuilding gcc from upstream everyday,
> there's not much more to do than wait.
>
> (You could adopt Andres' -g1 workaround, but then we'd not know
> when the gcc bug is fixed.  So unless this drags on quite awhile,
> I think alligator is best left as-is.)
>

It's been a few days since alligator lit up the buildfarm red. IMHO at this
point, it is just noise. So I've reduced its v16+ build frequency to daily
(instead of a few minutes). I'll revert that once gcc is fixed upstream.

-
robins

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Require sizeof(bool) == 1.

  2. If a C23 compiler is detected, try asking for C17.

  3. Fix C23 compiler warning

  4. Rename C23 keyword

  5. Assume that <stdbool.h> conforms to the C standard.

  6. Revise tree-walk APIs to improve spec compliance & silence warnings.