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

Robins Tharakan <tharakan@gmail.com>

From: Robins Tharakan <tharakan@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andrew Dunstan <andrew@dunslane.net>, 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-15T07:04:23Z
Lists: pgsql-bugs
On Sun, 15 Dec 2024 at 03:35, Tom Lane <tgl@sss.pgh.pa.us> wrote:

>
> Nowadays run_branches' check for whether there's something to do is
> cheap enough that it's not worth skipping.  So it's recommendable
> to just launch that every so often, and not complicate your life
> with manual per-branch scheduling.
>

Thanks for explaining / confirming.
I'll update the remaining machine configurations soon.

-
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.