On Wed, May 02, 2018 at 09:19:56PM -0400, Steven Rostedt wrote: > On Wed, 2 May 2018 13:45:58 -0700 > Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: > > > On Wed, 2 May 2018 10:17:07 -0400 Steven Rostedt <rostedt@xxxxxxxxxxx> 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 What about CONFIG_CC_OPTIMIZE_FOR_DEBUGGING? We alreay have CONFIG_CC_OPTIMIZE_FOR_SIZE and CONFIG_CC_OPTIMIZE_FOR_PERFORMANCE. And do we need to move it to existing configuration menu "General setup-> Compiler optimization level"? But I also want it appear in "kernel hacking" since this is a debug option. -- Thanks, Changbin Du
