Re: [PATCH 0/2] Initial ergonomic improvements to scripts/Kconfig.toolchain

[Kees Cook]

On Wed, Oct 07, 2026 at 06:48:40PM +0200, Nicolas Schier wrote:
> When I look into the resulting .config, I'd wish, these empty string
> kconfig symbols could be unset, e.g.
> 
>     # CONFIG_CC_OPT_WNO_FORMAT_TRUNCATION_NON_KPRINTF is not set
>     # CONFIG_CC_OPT_WNO_DEFAULT_CONST_INIT_UNSAFE is not set
>     CONFIG_CC_OPT_WNO_DANGLING_POINTER="-Wno-dangling-pointer"
>     CONFIG_CC_OPT_WVLA_LARGER_THAN="-Wvla-larger-than=1"
>     CONFIG_CC_HAS_WSTRINGOP_OVERFLOW=y
> 
> instead of the current:
> 
>     CONFIG_CC_OPT_WNO_FORMAT_TRUNCATION_NON_KPRINTF=""
>     CONFIG_CC_OPT_WNO_DEFAULT_CONST_INIT_UNSAFE=""
>     CONFIG_CC_OPT_WNO_DANGLING_POINTER="-Wno-dangling-pointer"
>     CONFIG_CC_OPT_WVLA_LARGER_THAN="-Wvla-larger-than=1"
>     CONFIG_CC_HAS_WSTRINGOP_OVERFLOW=y
> 
> but that would make things unneccessary more complicated, right now.

Yeah, it may be worth documenting somewhere that "CONFIG_CC_OPT_..."
will have empty strings, and if someone wants to test _availability_ of
a feature, they need to still create and use CONFIG_CC_HAS_... ?

-- 
Kees Cook