From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
cc: pgsql-hackers@lists.postgresql.org
Subject: Re: gcc 15 "array subscript 0" warning at level -O3
In-reply-to: <brpeo76nq4sb3wqkwbfjmy2b6mz5zgyoshwmqcbkmmpja5ydia@iadpnczghsyq>
References: <1985046.1745602635@sss.pgh.pa.us>
 <3prdb6hkep3duglhsujrn52bkvnlkvhc54fzvph2emrsm4vodl@77yy6j4hkemb>
 <brpeo76nq4sb3wqkwbfjmy2b6mz5zgyoshwmqcbkmmpja5ydia@iadpnczghsyq>
Comments: In-reply-to Andres Freund <andres@anarazel.de>
	message dated "Wed, 04 Jun 2025 15:00:03 -0400"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1317577.1749153048.1@sss.pgh.pa.us>
Date: Thu, 05 Jun 2025 15:50:48 -0400
Message-ID: <1317578.1749153048@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1317578.1749153048%40sss.pgh.pa.us>
Precedence: bulk

Andres Freund <andres@anarazel.de> writes:
>> I've been wondering about adding wrapping something like that in a
>> pg_assume(expr) or such.

> I've been once more annoyed by this warning. Here's a prototype for the
> approach outlined above.

Looks plausible by eyeball.  I did notice a typo in the comment:

+ * pg_assume(expr) stats that we assume `expr` to evaluate to true. In assert

s/stats/states/, I think you meant.

			regards, tom lane