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

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Álvaro Herrera <alvherre(at)kurilemu(dot)de>
Cc: Hans Buschmann <buschmann(at)nidsa(dot)net>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: PG19beta1: GCC 16.1.1 warning: ‘actual_arg_types’ may be used uninitialized in clauses.c
Date: 2026-06-17 14:39:18
Message-ID: ajKxliOE7JzBPQiR@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?

--
nathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2026-06-17 14:43:50 Re: Fix pg_restore --no-globals SQL output for pg_dumpall archives
Previous Message Nathan Bossart 2026-06-17 14:22:05 Re: Fix --missing-stats-only false positive for partitioned expression indexes