From: Pavel Machek <pavel@ucw.cz>
To: devnetfs <devnetfs@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: compiling kernel with debug and optimization
Date: Mon, 10 Feb 2003 20:23:24 +0100 [thread overview]
Message-ID: <20030210192324.GA154@elf.ucw.cz> (raw)
In-Reply-To: <20030210111151.31800.qmail@web20418.mail.yahoo.com>
Hi!
> Does compiling with -g option degrade performance? IMO it should NOT.
>
> If that's true, then why dont we compile kernels with both -g and -O2
> always?
Build with -g takes *a lot* of diskspace, like 1Gig.
Pavel
--
Worst form of spam? Adding advertisment signatures ala sourceforge.net.
What goes next? Inserting advertisment *into* email?
next prev parent reply other threads:[~2003-02-11 10:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-10 11:11 compiling kernel with debug and optimization devnetfs
2003-02-10 11:32 ` Keith Owens
2003-02-10 16:28 ` devnetfs
2003-02-10 19:23 ` Pavel Machek [this message]
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=20030210192324.GA154@elf.ucw.cz \
--to=pavel@ucw.cz \
--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