pg.ddx.io pgsql-bugs@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: tharakan@gmail.com, Peter Eisentraut <peter@eisentraut.org>
Cc: Sam James <sam@gentoo.org>
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: Build failure with GCC 15 (defaults to -std=gnu23)
Date: Wed, 27 Nov 2024 13:28:24 -0500
Message-ID: <1897695.1732732104@sss.pgh.pa.us> (raw )
In-Reply-To: <CA+hUKG+y2q0dP=g=bbkAWD66unrSKsQEc29ERvA_6fTC3b954Q@mail.gmail.com >
References: <87o72eo9iu.fsf@gentoo.org >
<3073930.1731867112@sss.pgh.pa.us >
<CA+hUKGJsuBiBcYnmJhGUNEg6Ud3n+C3K8c6em6RTOgu1E-dbwg@mail.gmail.com >
<3160019.1731875201@sss.pgh.pa.us >
<CA+hUKGLJnhpJBrsutH2aK91ARMS+XCez5P8XrR-kwdfSyLXGiQ@mail.gmail.com >
<3169079.1731880169@sss.pgh.pa.us >
<CA+hUKGJEnmapE7YYEfdJYZ-yGmcDpVGRrQ_eEVdcux26ZNJq_g@mail.gmail.com >
<3175762.1731883847@sss.pgh.pa.us >
<CA+hUKGJBNYAAYE51Ef-reKo1cUDvs3GgnChyh4ETqiSVQ0MR5w@mail.gmail.com >
<dec2bd5b-66e3-4750-83ef-e597d539c2f4@eisentraut.org >
<152145.1732116729@sss.pgh.pa.us >
<b906d958-4b37-47f3-9efb-79b575042661@eisentraut.org >
<CA+hUKGJma08NBfwv8kiLAW08wFaz-WxDuXWbENi92XdE46N6ZA@mail.gmail.com >
<485f5982-18c5-4210-9c7d-7c05453f7033@eisentraut.org >
<CA+hUKGL0LWK7hVO9r2eb3hFDBptZByOkAKGAjXKJ5mqd9hs_fA@mail.gmail.com >
<1447160.1732565223@sss.pgh.pa.us >
<CA+hUKG+5ErSyS2+rqx0bvKAWadP9NQBOsUgZVpz74ZB0DA=nJw@mail.gmail.com >
<1578470.1732587191@sss.pgh.pa.us >
<CA+hUKGLjA4AOajK4Twb9qT5gY=cqC2WJk3rVxEYFu=V5uiz6cw@mail.gm! ail.com >
<CA+hUKGJ4HEntEJkpqinyaLn3AfXMvCirWk0n2H4LWDxSSGh-Dw@mail.gmail.com >
<CA+hUKG+y2q0dP=g=bbkAWD66unrSKsQEc29ERvA_6fTC3b954Q@mail.gmail.com >
Thomas Munro <thomas.munro@gmail.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
view thread (42+ messages) latest in thread
Message-ID: <1897695.1732732104@sss.pgh.pa.us>
Permalink: ../1897695.1732732104@sss.pgh.pa.us/
Also on: postgresql.org/message-id/1897695.1732732104@sss.pgh.pa.us
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, thomas.munro@gmail.com, andres@anarazel.de, peter@eisentraut.org, sam@gentoo.org, pgsql-bugs@lists.postgresql.org
Subject: Re: Build failure with GCC 15 (defaults to -std=gnu23)
In-Reply-To: <1897695.1732732104@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox