From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, vbabka@suse.cz, peterz@infradead.org,
ndesaulniers@google.com, nathan@kernel.org,
michal.lkml@markovi.net, maskray@google.com,
masahiroy@kernel.org, linux@rasmusvillemoes.dk,
keescook@chromium.org, jpoimboe@kernel.org, isabbasso@riseup.net,
edumazet@google.com, dan.j.williams@intel.com,
dmitrii.bundin.a@gmail.com, akpm@linux-foundation.org
Subject: [to-be-updated] kbuild-add-debug-level-and-macro-defs-options.patch removed from -mm tree
Date: Fri, 30 Sep 2022 16:44:33 -0700 [thread overview]
Message-ID: <20220930234434.87B86C433C1@smtp.kernel.org> (raw)
The quilt patch titled
Subject: kbuild: add debug level and macro defs options
has been removed from the -mm tree. Its filename was
kbuild-add-debug-level-and-macro-defs-options.patch
This patch was dropped because an updated version will be merged
------------------------------------------------------
From: Dmitrii Bundin <dmitrii.bundin.a@gmail.com>
Subject: kbuild: add debug level and macro defs options
Date: Mon, 15 Aug 2022 04:33:17 +0300
Add config options to control debug info level and producing of macro
definitions for GCC/Clang.
Option DEBUG_INFO_LEVEL is responsible for controlling debug info level.
Before GCC 11 and Clang 12 -gsplit-dwarf implicitly uses -g2. To provide
a way to override the setting with, e.g. -g1, DEBUG_INFO_LEVEL is set
independently from DEBUG_INFO_SPLIT.
Option DEBUG_MACRO_DEFINITIONS is responsible for controlling inclusion of
macro definitions. Since Clang uses -fdebug-macro to control if macro
definitions are produced which is different from GCC, provides a
compiler-specific way of handling macro inclusion. The option is handled
after DEBUG_INFO_LEVEL since -g3 -g2 implies -g2, but -g2 -g3 implies -g3
and GCC uses -g3 to produce macro definitions.
Link: https://lkml.kernel.org/r/20220815013317.26121-1-dmitrii.bundin.a@gmail.com
Signed-off-by: Dmitrii Bundin <dmitrii.bundin.a@gmail.com>
Cc: Dan Williams <dan.j.williams@intel.com>
Cc: Eric Dumazet <edumazet@google.com>
Cc: Fangrui Song <maskray@google.com>
Cc: Isabella Basso <isabbasso@riseup.net>
Cc: Josh Poimboeuf <jpoimboe@kernel.org>
Cc: Kees Cook <keescook@chromium.org>
Cc: Masahiro Yamada <masahiroy@kernel.org>
Cc: Michal Marek <michal.lkml@markovi.net>
Cc: Nathan Chancellor <nathan@kernel.org>
Cc: Nick Desaulniers <ndesaulniers@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Vlastimil Babka <vbabka@suse.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
lib/Kconfig.debug | 20 ++++++++++++++++++++
scripts/Makefile.debug | 12 ++++++++++--
2 files changed, 30 insertions(+), 2 deletions(-)
--- a/lib/Kconfig.debug~kbuild-add-debug-level-and-macro-defs-options
+++ a/lib/Kconfig.debug
@@ -304,6 +304,26 @@ config DEBUG_INFO_REDUCED
DEBUG_INFO build and compile times are reduced too.
Only works with newer gcc versions.
+config DEBUG_INFO_LEVEL
+ int "Debug info level"
+ range 1 3
+ default "2"
+ help
+ Sets the level of how much debug information to generate (-glevel).
+ Level 1 produces minimal debug information without including information
+ about local variables. Level 3 includes extra information like macro
+ definitions. Setting up level 3 will require significantly more disk
+ space and increase built time.
+
+config DEBUG_MACRO_DEFINITIONS
+ bool "Add macro definitions to debug info"
+ default n
+ help
+ Generates macro definitions to provide a way to expand macros right
+ in the debugging session. This information can be used with macro expand,
+ info macro in gdb. This option is equivalent to setting -g3 in GCC and
+ -fdebug-macro in Clang.
+
config DEBUG_INFO_COMPRESSED
bool "Compressed debugging information"
depends on $(cc-option,-gz=zlib)
--- a/scripts/Makefile.debug~kbuild-add-debug-level-and-macro-defs-options
+++ a/scripts/Makefile.debug
@@ -2,8 +2,6 @@ DEBUG_CFLAGS :=
ifdef CONFIG_DEBUG_INFO_SPLIT
DEBUG_CFLAGS += -gsplit-dwarf
-else
-DEBUG_CFLAGS += -g
endif
ifndef CONFIG_AS_IS_LLVM
@@ -16,6 +14,16 @@ dwarf-version-$(CONFIG_DEBUG_INFO_DWARF5
DEBUG_CFLAGS += -gdwarf-$(dwarf-version-y)
endif
+DEBUG_CFLAGS += -g$(CONFIG_DEBUG_INFO_LEVEL)
+ifdef CONFIG_DEBUG_MACRO_DEFINITIONS
+ifdef CONFIG_CC_IS_GCC
+DEBUG_CFLAGS += -g3
+endif
+ifdef CONFIG_CC_IS_CLANG
+DEBUG_CFLAGS += -fdebug-macro
+endif
+endif
+
ifdef CONFIG_DEBUG_INFO_REDUCED
DEBUG_CFLAGS += -fno-var-tracking
ifdef CONFIG_CC_IS_GCC
_
Patches currently in -mm which might be from dmitrii.bundin.a@gmail.com are
reply other threads:[~2022-09-30 23:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220930234434.87B86C433C1@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=dmitrii.bundin.a@gmail.com \
--cc=edumazet@google.com \
--cc=isabbasso@riseup.net \
--cc=jpoimboe@kernel.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=masahiroy@kernel.org \
--cc=maskray@google.com \
--cc=michal.lkml@markovi.net \
--cc=mm-commits@vger.kernel.org \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=peterz@infradead.org \
--cc=vbabka@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.