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: 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 14:54:15
Message-ID: 1856779.1732719255@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:
> On Mon, Nov 18, 2024 at 2:59 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Yeah, that's a fair criticism. I don't think we've tested that code
>> path since I retired prairiedog, so who's to say that it works even
>> now? Maybe it's best to just delete that code, and if we ever find a
>> new platform with wider bool, figure out what to do at that time.

> Here's a draft patch for that.

Passes an eyeball check, but I've not really tried to test it.
I suppose the only meaningful test is likely to be letting the
buildfarm loose on it.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Nathan Bossart 2024-11-27 15:40:13 Re: BUG #18711: Attempting a connection with a database name longer than 63 characters now fails
Previous Message Alvaro Herrera 2024-11-27 12:53:07 Re: Function pg_get_constraintdef