public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: mmarek@suse.cz, linux-kbuild@vger.kernel.org,
	linux-kernel@vger.kernel.org, ak@linux.intel.com
Subject: [PATCH] Kbuild: Add option to set -femit-struct-debug-baseonly
Date: Wed, 14 Jul 2010 15:43:52 +0200	[thread overview]
Message-ID: <20100714134352.GA10341@basil.fritz.box> (raw)

Kbuild: Add option to set -femit-struct-debug-baseonly 

Newer gcc has a -femit-struct-debug-baseonly option that dramatically
reduces the size of object files with debug info. What it does
is to only emit type information for structures when the structures
are defined in the same file or in a header file.

This means the type information for most headers are not included.
This is not good when the type information is actually
needed (e.g. with kgdb or systemtap) 

But often kernel hackers only care about line numbers and don't
need all the type information anyways. In this case setting
the option can be a big win:

A build dir for a specific x86-64 configuration with gcc 4.5
shrunk from 2.3G to 1.2G. The compilation was also nearly a minute
faster.

Signed-off-by: Andi Kleen <ak@linux.intel.com>

---
 Makefile          |    4 ++++
 lib/Kconfig.debug |   12 ++++++++++++
 2 files changed, 16 insertions(+)

Index: linux-2.6.34-ak/Makefile
===================================================================
--- linux-2.6.34-ak.orig/Makefile
+++ linux-2.6.34-ak/Makefile
@@ -554,6 +554,10 @@ KBUILD_CFLAGS	+= -g
 KBUILD_AFLAGS	+= -gdwarf-2
 endif
 
+ifdef CONFIG_DEBUG_INFO_REDUCED
+KBUILD_CFLAGS 	+= $(call cc-option, -femit-struct-debug-baseonly)
+endif
+
 ifdef CONFIG_FUNCTION_TRACER
 KBUILD_CFLAGS	+= -pg
 endif
Index: linux-2.6.34-ak/lib/Kconfig.debug
===================================================================
--- linux-2.6.34-ak.orig/lib/Kconfig.debug
+++ linux-2.6.34-ak/lib/Kconfig.debug
@@ -616,6 +616,18 @@ config DEBUG_INFO
 
 	  If unsure, say N.
 
+config DEBUG_INFO_REDUCED
+	bool "Reduce debugging information"
+	depends on DEBUG_INFO
+	help
+	  If you say Y here gcc is instructed to generate less debugging information
+          for structure types. This means that tools that need full debugging information
+          (like kgdb or systemtap) won't be happy. But if you merely need debugging
+          information to resolve line numbers there is no loss.
+          Advantage is that build directory object sizes shrink dramatically over
+          a full DEBUG_INFO build and compile times are reduced too.
+          Only works with newer gcc versions.
+
 config DEBUG_VM
 	bool "Debug VM"
 	depends on DEBUG_KERNEL

             reply	other threads:[~2010-07-14 13:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-14 13:43 Andi Kleen [this message]
2010-07-14 15:22 ` [PATCH] Kbuild: Add option to set -femit-struct-debug-baseonly Michal Marek

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=20100714134352.GA10341@basil.fritz.box \
    --to=andi@firstfloor.org \
    --cc=ak@linux.intel.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox