Horton
Menu

Re: PG19beta1: GCC 16.1.1 warning: ‘actual_arg_types’ may be used uninitialized in clauses.c

Erik Rijkers <er@xs4all.nl>

View thread
From: Erik Rijkers <er@xs4all.nl>
To: Nathan Bossart <nathandbossart@gmail.com>, Álvaro Herrera <alvherre@kurilemu.de>
Cc: Hans Buschmann <buschmann@nidsa.net>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2026-06-17T15:27:35Z
Lists: pgsql-hackers 
Op 6/17/26 om 16:39 schreef Nathan Bossart:
> On Fri, Jun 12, 2026 at 04:54:04PM +0200, Álvaro Herrera wrote:
>> On 2026-Jun-04, Nathan Bossart wrote:
>>> This code is ~18 years old, so I'm dubious there's a real problem here.
>>> Does something like this suppress the warning?
>>>
>>> 	Oid			actual_arg_types[FUNC_MAX_ARGS] = {InvalidOid};
>>
>> I agree that it doesn't look like there's a real problem, and that
>> something like what you suggest should silence this warning.  I mildly
>> prefer to do " = {0}" though, the rules for C incomplete initializers
>> being so weird.  But I wouldn't oppose this patch as posted.
> 
> WFM.  Hans, can you confirm this fixes the issue?
> 

FWIW, it silences that warning on my gcc 16.1.0

Erik

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Silence "may be used uninitialized" compiler warning.