| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | John Naylor <john(dot)naylor(at)enterprisedb(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Debian 12 gcc warning |
| Date: | 2023-08-29 14:18:36 |
| Message-ID: | 1006857.1693318716@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Tue, Aug 29, 2023 at 10:26:27AM +0700, John Naylor wrote:
>> It looks like the former, since I can silence it on gcc 13 / -O1 by doing:
>> /* keep compiler quiet */
>> actual_arg_types[0] = InvalidOid;
> Agreed, that fixes it for me too. In fact, assigning to only element 99 or
> 200 also prevents the warning, and considering the array is defined for
> 100 elements, the fact is accepts 200 isn't a good thing. Patch attached.
That seems like a pretty clear compiler bug, particularly since it just
appears in this one version. Rather than contorting our code, I'd
suggest filing a gcc bug.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2023-08-29 14:22:32 | Re: Eager page freeze criteria clarification |
| Previous Message | Tom Lane | 2023-08-29 14:14:45 | Re: Restoring default privileges on objects |