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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, tharakan(at)gmail(dot)com, 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-27 18:28:24
Message-ID: 1897695.1732732104@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Thomas Munro <thomas(dot)munro(at)gmail(dot)com> writes:
> Pushed. Alligator is turning green in the back branches, only one more to go.
> I see that Peter also pushed the reserved word patches. Apparently
> that gcc bug it's blowing up on might go away with -g0 (see link
> earlier), but anyway it's a nightly build compiler so fingers crossed
> for a fix soon. The newer branches are building and running for me on
> { gcc14, gcc15, clang18 } -std=gnu23, and apparently the bug was even
> in gcc14, so it must require some unlikely conditions that alligator
> has stumbled on.

Looks like flaviventris and serinus just updated to the same broken
compiler version that alligator is using :-(. Maybe we'd better
file a formal bug report?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andres Freund 2024-11-27 18:50:59 Re: Build failure with GCC 15 (defaults to -std=gnu23)
Previous Message Tom Lane 2024-11-27 18:17:18 Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails