mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Keith Owens <kaos@ocs.com.au>
To: devnetfs <devnetfs@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: compiling kernel with debug and optimization
Date: Mon, 10 Feb 2003 22:32:37 +1100	[thread overview]
Message-ID: <2721.1044876757@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "Mon, 10 Feb 2003 03:11:51 -0800." <20030210111151.31800.qmail@web20418.mail.yahoo.com>

On Mon, 10 Feb 2003 03:11:51 -0800 (PST), 
devnetfs <devnetfs@yahoo.com> wrote:
>Does compiling with -g option degrade performance? IMO it should NOT.

Compiling with -g slows down compilation and link, mainly because of
the extra debugging data that has to be copied around.  -g
significantly increases disk usage.

>If that's true, then why dont we compile kernels with both -g and -O2
>always? Also does using -g AND -O2 cause some optimizations to be 
>missed out?

With gcc, compiling with -g should have no effect on the kernel.  One
of my occasional tests is to build vmlinux with and without -g, run
both through strip -g and compare the results.  They should be
identical except for the build timestamp.


  reply	other threads:[~2003-02-10 11:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-10 11:11 devnetfs
2003-02-10 11:32 ` Keith Owens [this message]
2003-02-10 16:28   ` devnetfs
2003-02-10 19:23 ` Pavel Machek
2003-02-12  5:20   ` devnetfs
     [not found] <20030210111151.31800.qmail@web20418.mail.yahoo.com.suse.lists.linux.kernel>
     [not found] ` <20030210192324.GA154@elf.ucw.cz.suse.lists.linux.kernel>
2003-02-11 11:11   ` Andi Kleen

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=2721.1044876757@ocs3.intra.ocs.com.au \
    --to=kaos@ocs.com.au \
    --cc=devnetfs@yahoo.com \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®