Re: Build failure with GCC 15 (defaults to -std=gnu23) - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Build failure with GCC 15 (defaults to -std=gnu23)
Date
Msg-id 1578470.1732587191@sss.pgh.pa.us
Whole thread Raw
In response to Re: Build failure with GCC 15 (defaults to -std=gnu23)  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: Build failure with GCC 15 (defaults to -std=gnu23)
List pgsql-bugs
Thomas Munro <thomas.munro@gmail.com> writes:
> ... I think it might be unlikely to
> upset anyone if it works something like this:

> * For 16+ nothing, we're going to be C23 clean (after a couple more
> back-patches)
> * For 9.2-15 on GCC < 15 it'll stay as nothing too
> * For 9.2-15 on early GCC 15 adopter distros like Fedora/Gentoo etc
> we'll detect C23, and perhaps start spitting out -std=c17 (if you've
> detected C23, I think you can assume that C17 is available so we don't
> have to do a C17-C11-C99[-C89] search?)
> * When 12-15 fall out of support and all compilers are eventually C23+
> compilers, they'll eventually always be getting -std=c17 by the above
> rules but no one will mind about that in the ancient branches

Sounds plausible to me.  Will you work on making that happen?

            regards, tom lane



pgsql-bugs by date:

Previous
From: Thomas Munro
Date:
Subject: Re: Build failure with GCC 15 (defaults to -std=gnu23)
Next
From: Noah Misch
Date:
Subject: Re: 'WARNING: you don't own a lock of type ExclusiveLock' is printed during the GRANT command on PostgreSQL16.5