Re: New string-truncation warnings from GCC 15

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: New string-truncation warnings from GCC 15
Date: 2025-09-17 21:22:27
Message-ID: ns5kbonarnq4ocp7y4v5q27476pfufjrc6ktuchcjyezcfmdke@tnuyobpgjbsy
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2025-09-17 17:00:42 -0400, Tom Lane wrote:
> Andres Freund <andres(at)anarazel(dot)de> writes:
> > On 2025-09-17 16:38:56 -0400, Tom Lane wrote:
> >> Oh! Hmm... I am not sure that we want to commit to being -Wextra
> >> clean across-the-board.
>
> > We've been -Wextra clean for years, with a few temporary exceptions. IME a lot
> > of warnings added to -Wextra in one year, get promoted to -Wall a few releases
> > later. I found plenty mistakes with -Wextra stuff, so I'd be sad if we decided
> > we're not trying to fix them...
>
> Well, we should either commit to it (and put -Wextra into our
> standard switches) or not.

I'd be mildly worried about -Wextra in older compilers (and clang, but just
because I don't regularly track -Wextra with clang). But I'd be up for trying
it out.

A slightly more targeted approach would be to add -Wstringop-truncation to our
explicitly enabled warnings...

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-09-17 21:26:50 Re: New string-truncation warnings from GCC 15
Previous Message Bruce Momjian 2025-09-17 21:05:38 Re: REPACK and naming