Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <CANXV_XwgZMCGXijfoUyZ9+KyM6Rgeqiq-sCfubyj_16d-2CN=A@mail.gmail.com>
 <20220815013317.26121-1-dmitrii.bundin.a@gmail.com> <CAK7LNAQzVto=rEpASc-JOF_TW0KhNT93jD0E2gfk8UES3PWFiw@mail.gmail.com>
In-Reply-To: <CAK7LNAQzVto=rEpASc-JOF_TW0KhNT93jD0E2gfk8UES3PWFiw@mail.gmail.com>
From:   Dmitrii Bundin <dmitrii.bundin.a@gmail.com>
Date:   Thu, 18 Aug 2022 21:57:02 +0300
Message-ID: <CANXV_XzGHQ8_X2t37DwRjS7kKFX0kWDpwHEg3k+zZ4YfV98gjw@mail.gmail.com>
Subject: Re: [PATCH v3] kbuild: add debug level and macro defs options
To:     Masahiro Yamada <masahiroy@kernel.org>
Cc:     Andrew Morton <akpm@linux-foundation.org>,
        Dan Williams <dan.j.williams@intel.com>,
        Eric Dumazet <edumazet@google.com>,
        Isabella Basso <isabbasso@riseup.net>,
        Josh Poimboeuf <jpoimboe@kernel.org>,
        Kees Cook <keescook@chromium.org>,
        Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Rasmus Villemoes <linux@rasmusvillemoes.dk>,
        =?UTF-8?B?Ru+/ve+/ve+/vW5nLXJ177+977+977+9IFPvv73vv73vv71uZw==?= 
        <maskray@google.com>, Michal Marek <michal.lkml@markovi.net>,
        Nathan Chancellor <nathan@kernel.org>,
        Nick Desaulniers <ndesaulniers@google.com>,
        "Peter Zijlstra (Intel)" <peterz@infradead.org>,
        Vlastimil Babka <vbabka@suse.cz>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Thu, Aug 18, 2022 at 7:14 AM Masahiro Yamada <masahiroy@kernel.org> wrote:
>
> -g1 is only possible via DEBUG_INFO_LEVEL, but
> presumably it is not your main interest
> (and not sure if there is anybody interested)
> because the main motivation for your v1
> is to generate macro debug data.

I tested the build process with -g1 and it turned out to generate an
image that is 20% lesser in size.
This is indeed not really my use-case, but are you sure it might not
be helpful in general?

The reason to add DEBUG_INFO_LEVEL was also motivated by the
GCC11+/Clang12+ behavior of -gsplit-dwarf to provide an orthogonal
debug level config.
"The later -g<level> wins" behavior in turns works identically for
both older and newer compiler versions so such an implementation
provides version independent build behavior.
Testing on gcc-11, -gdwarf-<level>/-gdwarf still implies -g2.
It seemed a clearer way to me to explicitly set a debug level that
just wins instead of relying on implicits.

Regards
Dmitrii