[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180502211956.6c9e8d7b@vmware.local.home>
Date: Wed, 2 May 2018 21:19:56 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: changbin.du@...el.com, yamada.masahiro@...ionext.com,
michal.lkml@...kovi.net, tglx@...utronix.de, mingo@...hat.com,
rdunlap@...radead.org, x86@...nel.org, lgirdwood@...il.com,
broonie@...nel.org, arnd@...db.de, linux-kbuild@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org
Subject: Re: [PATCH v2 4/5] kernel hacking: new config DEBUG_EXPERIENCE to
apply GCC -Og optimization
On Wed, 2 May 2018 13:45:58 -0700
Andrew Morton <akpm@...ux-foundation.org> wrote:
> On Wed, 2 May 2018 10:17:07 -0400 Steven Rostedt <rostedt@...dmis.org> wrote:
>
> > > Comparison of vmlinux size: a bit smaller.
> > >
> > > w/o CONFIG_DEBUG_EXPERIENCE
> >
> > I hate the config name.
> >
> > I probably can't come up with better ones but let's try:
> >
> > CONFIG_DEBUG_OPTIMIZE ?
> > CONFIG_OPTIMIZE_DEBUG ?
> >
> > But "EXPERIENCE" sounds like I'm on some DEBUG LSD.
>
> Metoo, but the gcc people decided on "-Og: Optimize debugging
> experience ..." and I think there are benefits if the kernel is to
> align the naming with that.
I still see that as "Optimize debugging" and "experience" is just the
platform of what was done.
With that gcc comment, I still think CONFIG_OPTIMIZE_DEBUG is more
inline with what it is and understandable than
CONFIG_DEBUG_EXPERIENCE. The "OPTIMIZE" is the key word there.
-- Steve
Powered by blists - more mailing lists