Re: Debian 12 gcc warning
От | Bruce Momjian |
---|---|
Тема | Re: Debian 12 gcc warning |
Дата | |
Msg-id | ZO6u1hySX4lBI/31@momjian.us обсуждение исходный текст |
Ответ на | Re: Debian 12 gcc warning (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Debian 12 gcc warning
|
Список | pgsql-hackers |
On Tue, Aug 29, 2023 at 10:18:36AM -0400, Tom Lane wrote: > Bruce Momjian <bruce@momjian.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. I assume I have to create a test case to report this to the gcc team. I tried to create such a test case on gcc 12 but it doesn't generate the warning. Attached is my attempt. Any ideas? I assume we can't just tell them to download our software and compile it. -- Bruce Momjian <bruce@momjian.us> https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you.
Вложения
В списке pgsql-hackers по дате отправления: