From: Tom Lane <tgl@sss.pgh.pa.us>
To: Robins Tharakan <tharakan@gmail.com>
cc: 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
Subject: Re: Build failure with GCC 15 (defaults to -std=gnu23)
In-reply-to: 
 <CAEP4nAw4UHSgcHFL7Rsub0nCHW=6ZCrpiuBUT_dV5+4apS=Q5Q@mail.gmail.com>
References: <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+hUKGJ4HEntEJkpqinyaLn3AfXMvCirWk0n2H4LWDxSSGh-Dw@mail.gmail.com>
 <CA+hUKG+y2q0dP=g=bbkAWD66unrSKsQEc29ERvA_6fTC3b954Q@mail.gmail.com>
 <1897695.1732732104@sss.pgh.pa.us>
 <eu34f6armrlbq7cdai3dy45576h3qybme47uxens4cowpghzqe@52owmagijfiu>
 <2gao2zapw2dumahxgma4t3c6cquy4vnjs5bt4yvduexpywwm2m@3uhxxc63xvlq>
 <CAEP4nAw4UHSgcHFL7Rsub0nCHW=6ZCrpiuBUT_dV5+4apS=Q5Q@mail.gmail.com>
Comments: In-reply-to Robins Tharakan <tharakan@gmail.com>
	message dated "Fri, 29 Nov 2024 16:56:06 +1030"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <494521.1732894313.1@sss.pgh.pa.us>
Date: Fri, 29 Nov 2024 10:31:53 -0500
Message-ID: <494522.1732894313@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/494522.1732894313%40sss.pgh.pa.us>
Precedence: bulk

Robins Tharakan <tharakan@gmail.com> writes:
> alligator/HEAD is still failing though.
> Let me know if changing something on alligator can help in some way.

I think we're waiting on the gcc crew to fix their bug.  As long
as alligator is faithfully rebuilding gcc from upstream everyday,
there's not much more to do than wait.

(You could adopt Andres' -g1 workaround, but then we'd not know
when the gcc bug is fixed.  So unless this drags on quite awhile,
I think alligator is best left as-is.)

			regards, tom lane