Re: gcc 13 warnings

From: Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: gcc 13 warnings
Date: 2023-03-29 07:51:19
Message-ID: ea8b5e6d-442e-cb7e-75a5-12acc789801c@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 22.03.23 10:45, Peter Eisentraut wrote:
> On 18.03.23 00:54, Andres Freund wrote:
>>> I think a good compromise would be buildtype=debugoptimized, which is
>>> -O2
>>> with debug symbols, which also sort of matches the default in the
>>> autoconf
>>> world.
>>
>> Looks like that'd result in a slightly worse build with msvc, as
>> afaict we
>> wouldn't end up with /OPT:REF doesn't get specified, which
>> automatically gets
>> disabled if /DEBUG is specified. I guess we can live with that.
>
> I looked up what /OPT:REF does
> (https://learn.microsoft.com/en-us/cpp/build/reference/opt-optimizations?view=msvc-170), and it seems pretty obscure to me, at least for development builds.

I have committed the change of buildtype to debugoptimized.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2023-03-29 08:28:22 Re: "variable not found in subplan target list"
Previous Message Peter Eisentraut 2023-03-29 07:08:05 Re: TAP output format in pg_regress