On Mon, Nov 25, 2024 at 10:27 AM Masahiro Yamada <masahiroy@xxxxxxxxxx> wrote: > > On Mon, Nov 25, 2024 at 12:59 AM Thomas Weißschuh <linux@xxxxxxxxxxxxxx> 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. > Presumably, DEBUG_INFO_BTF is the one because you submitted some patches at the same time. Are there some compile errors that are not detected when DEBUG_INFO_BTF is disabled? -- Best Regards Masahiro Yamada
