linux-kernel - Re: [PATCH] kconfig: prefer toolchain default for debug information choice

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAK7LNARURUizjHNhCKjdLSJp1mCF0HYvyOfm7n8LHmUBjYByQw@mail.gmail.com>
Date: Mon, 25 Nov 2024 10:27:21 +0900
From: Masahiro Yamada <masahiroy@...nel.org>
To: Thomas Weißschuh <linux@...ssschuh.net>
Cc: Andrew Morton <akpm@...ux-foundation.org>, linux-kernel@...r.kernel.org, 
	Nathan Chancellor <nathan@...nel.org>, Nicolas Schier <nicolas@...sle.eu>, linux-kbuild@...r.kernel.org
Subject: Re: [PATCH] kconfig: prefer toolchain default for debug information choice

On Mon, Nov 25, 2024 at 12:59 AM Thomas Weißschuh <linux@...ssschuh.net> wrote:
>
> Kconfig by default chooses the first entry of a choice setting.
> For the "debug information" choice this is DEBUG_INFO_NONE which
> disables debug information completely.
>
> The kconfig choice itself recommends to use "Toolchain default":
>
>         Choose which version of DWARF debug info to emit. If unsure,
>         select "Toolchain default".
>
> Align the actual configuration with the recommendation by providing an
> explicit default.
>
> This also enables more codepaths from allmodconfig/allyesconfig which
> depend on debug information being available.

Please give me some examples for "more codepaths" enabled by DEBUG_INFO
because this is the opposite to the previous decision.


Commit f9b3cd24578401e7a392974b3353277286e49cee mentions:

  all*config target ends up taking much longer and the output is much larger.
  Having this be "default off" makes sense.



allmodconfig is often used for compile testing in CI/CD.
We need to see the sufficient gain that sacrifices
the build speed.



--
Best Regards
Masahiro Yamada