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

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, Sam James <sam(at)gentoo(dot)org>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: Build failure with GCC 15 (defaults to -std=gnu23)
Date: 2024-11-26 11:24:29
Message-ID: CA+hUKGJ4HEntEJkpqinyaLn3AfXMvCirWk0n2H4LWDxSSGh-Dw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Nov 26, 2024 at 3:25 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> On Tue, Nov 26, 2024 at 3:13 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > Sounds plausible to me. Will you work on making that happen?
>
> OK, trying it out...

Attached first attempt seems to work OK, tested on 9.2 and 15
branches. I'm not sure if it's the best way to test, or in the best
place, etc, ideas welcome. The reason for testing with > 201710
rather than >= 202311 is that there are some funny in between numbers
floating around: gcc14 -std=c23 -> 202000 (since you mentioned you'd
tested with that before), while gcc15 -std=c23 -> 202311 (the real
final standard number). Also tested v15 with clang18 -std=c23, which
breaks, and is fixed, as expected.

Attachment Content-Type Size
v1-15-0001-If-a-C23-compiler-is-detected-try-asking-for-C.patch application/octet-stream 4.4 KB
v1-9.2-0001-If-a-C23-compiler-is-detected-try-asking-for-.patch application/octet-stream 5.9 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Thomas Munro 2024-11-27 01:58:39 Re: pg_rewind fails on Windows where tablespaces are used
Previous Message Иван Ситников 2024-11-26 10:33:57 Re: BUG #18724: High data disk utilization during log writing