Re: patch: Use pg_assume in jsonb_util.c to fix GCC 15 warnings

Поиск
Список
Период
Сортировка
Искать
От
Peter Eisentraut
Тема
Re: patch: Use pg_assume in jsonb_util.c to fix GCC 15 warnings
Дата
Msg-id
a094061a-525e-4d9e-88db-2035a933e0e8@eisentraut.org
Ответ на
Список
Дерево обсуждения
patch: Use pg_assume in jsonb_util.c to fix GCC 15 warnings Dmitry Mityugov <d.mityugov@postgrespro.ru>
Re: patch: Use pg_assume in jsonb_util.c to fix GCC 15 warnings Tom Lane <tgl@sss.pgh.pa.us>
Re: patch: Use pg_assume in jsonb_util.c to fix GCC 15 warnings Andres Freund <andres@anarazel.de>
Re: patch: Use pg_assume in jsonb_util.c to fix GCC 15 warnings Tom Lane <tgl@sss.pgh.pa.us>
Re: patch: Use pg_assume in jsonb_util.c to fix GCC 15 warnings Tom Lane <tgl@sss.pgh.pa.us>
Re: patch: Use pg_assume in jsonb_util.c to fix GCC 15 warnings Peter Geoghegan <pg@bowt.ie>
Re: patch: Use pg_assume in jsonb_util.c to fix GCC 15 warnings Tom Lane <tgl@sss.pgh.pa.us>
Re: patch: Use pg_assume in jsonb_util.c to fix GCC 15 warnings Peter Geoghegan <pg@bowt.ie>
Re: patch: Use pg_assume in jsonb_util.c to fix GCC 15 warnings Tom Lane <tgl@sss.pgh.pa.us>
Re: patch: Use pg_assume in jsonb_util.c to fix GCC 15 warnings Peter Geoghegan <pg@bowt.ie>
Re: patch: Use pg_assume in jsonb_util.c to fix GCC 15 warnings Tom Lane <tgl@sss.pgh.pa.us>
Re: patch: Use pg_assume in jsonb_util.c to fix GCC 15 warnings Peter Geoghegan <pg@bowt.ie>
Re: patch: Use pg_assume in jsonb_util.c to fix GCC 15 warnings Peter Eisentraut <peter@eisentraut.org>
Re: patch: Use pg_assume in jsonb_util.c to fix GCC 15 warnings Erik Rijkers <er@xs4all.nl>
On 16.07.25 01:35, Peter Geoghegan wrote:
> On Sat, Jul 12, 2025 at 1:55 PM Andres Freund  wrote:
>> I had played with using pg_assume here too, but I couldn't really convince
>> myself that it's a good idea...
> 
> In the past, it was often necessary to work around MSVC's inability to
> see that a block containing elog(ERROR) doesn't actually need to
> initialize variables that'll never actually be used in code that comes
> after that block. We still have many "keep compiler quiet" variable
> initializations due to this.
> 
> Is that still something that we need to worry about? I don't recall
> running into it in quite a few years, though that might just be a
> coincidence.

Yes, this continues to be an unsolved problem.  See here for a recent 
discussion: 
https://www.postgresql.org/message-id/CAApHDvrFdXjbrV6KCx_GHKYSufUbNDYSsjppcJQiGOURfJE6qg@mail.gmail.com



В списке pgsql-hackers по дате отправления
От: John Naylor
Дата:
От: Ajin Cherian
Дата:
FAQ