Re: compiler warnings with gcc 4.8 and -Og

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Justin Pryzby <pryzby(at)telsasoft(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Melanie Plageman <melanieplageman(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Subject: Re: compiler warnings with gcc 4.8 and -Og
Date: 2022-06-02 13:32:10
Message-ID: B1CCBCDD-9764-49B9-81C4-A41A66B860B7@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 2 Jun 2022, at 07:09, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> I'm a little dubious about whether -Og is a case we should pay special
> attention to? Our standard optimization setting for gcc is -O2, and
> once you go away from that there are any number of weird cases that
> may or may not produce warnings.

I think we should pick one level to keep warning free, and stick to that. In
light of that, -O2 seems a lot more appealing than -Og.

--
Daniel Gustafsson https://vmware.com/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2022-06-02 13:51:51 Re: [PATCH] Expose port->authn_id to extensions and triggers
Previous Message Aleksander Alekseev 2022-06-02 13:30:20 Re: [PATCH] Compression dictionaries for JSONB