| From: | Erik Rijkers <er(at)xs4all(dot)nl> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, Á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 15:27:35 |
| Message-ID: | dd1352c0-baf6-1a5b-8342-570ef9126777@xs4all.nl |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ZizhuanLiu X-MAN | 2026-06-17 15:28:02 | Re: Improving psql autocompletion for SET LOCAL / SET SESSION |
| Previous Message | Tom Lane | 2026-06-17 15:05:30 | Re: [PATCH] Fix segmentation fault and infinite loop in jsonb_{plperl,plpython} |