pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Nathan Bossart <nathandbossart@gmail.com>
To: Álvaro Herrera <alvherre@kurilemu.de>
Cc: Hans Buschmann <buschmann@nidsa.net>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: PG19beta1: GCC 16.1.1 warning: ‘actual_arg_types’ may be used uninitialized in clauses.c
Date: Wed, 17 Jun 2026 09:39:18 -0500
Message-ID: <ajKxliOE7JzBPQiR@nathan> (raw)
In-Reply-To: <aiwb1wzWn-q1LNti@alvherre.pgsql>
References: <aiGUxEzo4o5_fRIq@nathan>
	<aiwb1wzWn-q1LNti@alvherre.pgsql>

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





view thread (5+ messages)  latest in thread

Message-ID: <ajKxliOE7JzBPQiR@nathan>
Permalink:  ../ajKxliOE7JzBPQiR@nathan/
Also on:    postgresql.org/message-id/ajKxliOE7JzBPQiR@nathan

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: nathandbossart@gmail.com, alvherre@kurilemu.de, buschmann@nidsa.net
  Subject: Re: PG19beta1: GCC 16.1.1 warning: ‘actual_arg_types’ may be used uninitialized in clauses.c
  In-Reply-To: <ajKxliOE7JzBPQiR@nathan>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox