From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> |
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>, PostgreSQL Hackers <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>, Daniel Gustafsson <daniel(at)yesql(dot)se> |
Subject: | Re: compiler warnings with gcc 4.8 and -Og |
Date: | 2022-06-02 14:33:52 |
Message-ID: | 967612.1654180432@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com> writes:
> On Thu, 2 Jun 2022, 07:10 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?
> The "Developer FAQ" page on the wiki suggests that when you develop
> with gcc that you use CFLAGS="-ggdb -Og -g3 -fno-omit-frame-pointer"
> during development, so I'd hardly call -Og "any random option".
I have no idea who wrote that FAQ entry, and I'd certainly not
accept it as being project policy. I'd actually say that's an
excellent example of adding some random compiler options.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Stark | 2022-06-02 14:58:33 | Re: PostgreSQL Limits: maximum number of columns in SELECT result |
Previous Message | Matthias van de Meent | 2022-06-02 14:27:25 | Re: compiler warnings with gcc 4.8 and -Og |