All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: Why sim/boot in -test4?
Date: Mon, 25 Aug 2003 20:56:46 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106184533520478@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106164660606242@msgid-missing>

>>>>> On Sat, 23 Aug 2003 18:40:55 +0100, Matthew Wilcox <willy@debian.org> said:

  Matthew> By the way, -test3 used to take a really really long time
  Matthew> to link each step, and -test4 doesn't.  I don't know
  Matthew> whether this was an intentional fix, but I'm certainly
  Matthew> happy to see it.

I don't think it's a fix per se, but rather a new config option: it
used to be that I turned on compilation with "-g" unconditionally
(sorry, but I hate not having debug info around when you need it...).
Now Sam (finally! ;-) added a CONFIG_DEBUG_KERNEL option, so if you
didn't turn this on, the kernel will be compiled without debug option
and the resulting object files will be a lot smaller.

BTW: someone really ought to look into why the debug info is so big
and what could be done to handle it more sanely.  For example, we get
tons of debug-info replication due to header-files etc.  It's rather
embarrassing how low the state of the art is w.r.t. debug info
management...

	--david

      parent reply	other threads:[~2003-08-25 20:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-23 13:49 Why sim/boot in -test4? Matthew Wilcox
2003-08-23 17:32 ` David Mosberger
2003-08-23 17:40 ` Matthew Wilcox
2003-08-25 20:56 ` David Mosberger [this message]

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=marc-linux-ia64-106184533520478@msgid-missing \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@vger.kernel.org \
    /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.