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-13T02:01:34Z
Lists: pgsql-bugs 
On Fri, 13 Dec 2024 at 11:52, Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Robins Tharakan <tharakan@gmail.com> writes:
> > 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.
>
> Looks like alligator just went green with the 20241212 gcc build.
>


Nice! Just forced REL_17_STABLE / REL_16_STABLE and they are past
that failure point too (still running).

For now I've restored the original build frequency for these branches.
 -
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.