Re: [PATCH] Add -Og optimization level - optimize for compile-time/debugging experience

2012-09-29 Thread Eric Botcazou
> Which means that -O0 should also set optimize_debug to 1? -O0 is > then !optimize && optimize_debug and -Og is optimize == 1 && > optimize_debug. That sounds more confusing than helpful though. Adding (|| optimize_debug) in the relevant places is probably good enough. -- Eric Botcazou

Re: [PATCH] Add -Og optimization level - optimize for compile-time/debugging experience

2012-09-19 Thread Richard Guenther
On Tue, 18 Sep 2012, Ian Lance Taylor wrote: > On Tue, Sep 18, 2012 at 4:23 AM, Richard Guenther wrote: > > > > This adds -Og as optimization level targeted at the devel-compile-debug > > cycle (formerly mostly tied to -O0 due to debug issues with even -O1). > > This needs an entry in gcc-4.8/ch

Re: [PATCH] Add -Og optimization level - optimize for compile-time/debugging experience

2012-09-19 Thread Richard Guenther
On Wed, 19 Sep 2012, Eric Botcazou wrote: > > This adds -Og as optimization level targeted at the devel-compile-debug > > cycle (formerly mostly tied to -O0 due to debug issues with even -O1). > > > > Discussion on g...@gcc.gnu.org at least shows interest in this, so this > > is a formal patch su

Re: [PATCH] Add -Og optimization level - optimize for compile-time/debugging experience

2012-09-19 Thread Eric Botcazou
> This adds -Og as optimization level targeted at the devel-compile-debug > cycle (formerly mostly tied to -O0 due to debug issues with even -O1). > > Discussion on g...@gcc.gnu.org at least shows interest in this, so this > is a formal patch submission with a request for comments on the > impleme

Re: [PATCH] Add -Og optimization level - optimize for compile-time/debugging experience

2012-09-18 Thread Ian Lance Taylor
On Tue, Sep 18, 2012 at 4:23 AM, Richard Guenther wrote: > > This adds -Og as optimization level targeted at the devel-compile-debug > cycle (formerly mostly tied to -O0 due to debug issues with even -O1). This needs an entry in gcc-4.8/changes.html, of course. Ian

Re: [PATCH] Add -Og optimization level - optimize for compile-time/debugging experience

2012-09-18 Thread Ian Lance Taylor
On Tue, Sep 18, 2012 at 4:23 AM, Richard Guenther wrote: > > 2012-09-18 Richard Guenther > > PR other/53316 > * common.opt (optimize_debug): New variable. > (Og): New optimization level. > * doc/invoke.texi (Og): Document. > * opts.c (maybe_default_option

Re: [PATCH] Add -Og optimization level - optimize for compile-time/debugging experience

2012-09-18 Thread Jakub Jelinek
On Tue, Sep 18, 2012 at 02:38:27PM +0200, Richard Guenther wrote: > > Glibc must be compiled with optimization. Will -Og build glibc? > > Apply the patch and check for yourself. I suppose the answer will > be yes (whatever "optimization" requirements glibc has). glibc headers check __OPTIMIZE__

Re: [PATCH] Add -Og optimization level - optimize for compile-time/debugging experience

2012-09-18 Thread Richard Guenther
On Tue, 18 Sep 2012, H.J. Lu wrote: > On Tue, Sep 18, 2012 at 4:23 AM, Richard Guenther wrote: > > > > This adds -Og as optimization level targeted at the devel-compile-debug > > cycle (formerly mostly tied to -O0 due to debug issues with even -O1). > > > > Discussion on g...@gcc.gnu.org at least

Re: [PATCH] Add -Og optimization level - optimize for compile-time/debugging experience

2012-09-18 Thread H.J. Lu
On Tue, Sep 18, 2012 at 4:23 AM, Richard Guenther wrote: > > This adds -Og as optimization level targeted at the devel-compile-debug > cycle (formerly mostly tied to -O0 due to debug issues with even -O1). > > Discussion on g...@gcc.gnu.org at least shows interest in this, so this > is a formal pa

[PATCH] Add -Og optimization level - optimize for compile-time/debugging experience

2012-09-18 Thread Richard Guenther
This adds -Og as optimization level targeted at the devel-compile-debug cycle (formerly mostly tied to -O0 due to debug issues with even -O1). Discussion on g...@gcc.gnu.org at least shows interest in this, so this is a formal patch submission with a request for comments on the implementation (no