lkml.org 
[lkml]   [2014]   [Feb]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] Clarify CONFIG_DEBUG_INFO's bloaty nature
On Mon, 3 Feb 2014, Andrew Morton wrote:

> > > How do you define "huge bloat" if the size of vmlinux doesn't increase?
> >
> > Don't be silly. The size of all the object files increase *hugely*.
>
> yup, I disable this in my allmodconfig testing, to great effect.
>
> That being said, I do think the text should make clear that the bloat
> is a compile-time impact and not a runtime one. Something like
>
> --- a/lib/Kconfig.debug~lib-kconfigdebug-clarify-config_debug_infos-bloaty-nature-fix
> +++ a/lib/Kconfig.debug
> @@ -128,9 +128,9 @@ config DEBUG_INFO
> tools like crash, kgdb, LKCD, gdb, etc on the kernel.
>
> If you only want to have resolved symbols in kernel traces and
> - are not going to need support for those tools above, you don't need
> - to enable this as it is a huge bloat and build slowdown;
> - enable CONFIG_KALLSYMS instead.
> + are not going to need support for the above tools, you don't need
> + to enable this. It hugely bloat object files' on-disk sizes and slows
> + the build. Enable CONFIG_KALLSYMS instead.
>
> If unsure, say N.
>

Um, I still don't think this is right since CONFIG_DEBUG_INFO_REDUCED
requires you to say yes here and that config option actually specifies
the tools for which it is effective. Are you suggesting that we decouple
CONFIG_DEBUG_INFO from CONFIG_DEBUG_INFO_REDUCED and make
CONFIG_DEBUG_INFO select the reduced variant? Or... what?


\
 
 \ /
  Last update: 2014-02-04 01:41    [W:0.072 / U:0.184 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site