From: "Kevin P. Fleming" <kpfleming@cox.net>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [2.6 patch] add an -Os config option
Date: Tue, 12 Aug 2003 09:03:16 -0700 [thread overview]
Message-ID: <3F390FC4.9000300@cox.net> (raw)
In-Reply-To: <3F390B36.5050709@techsource.com>
Timothy Miller wrote:
> Furthermore, it may be that we could benefit from compiling some source
> files with -Os and others with -O2, depending on how critical they are
> and how much they are ACTUALLY affected.
>
At one time last year, there was a brief discussion about modifying
the kernel's build process to make it build whole directories of
sources as a single "compilation unit". As I remember, this allowed
the compiler to make better decisions about how to organize the
resulting code, what to keep/discard, optimization, etc.
With the simplifications that have already occurred in the 2.6
makefiles, it seems to me that this would be an easier thing to do now
(as opposed to the old makefiles where the build process had a harder
time figuring out what source files were going to end up in the same
object file). Now that kbuild always builds "built-on.o" in each
source directory, could it perform that step by actually feeding gcc
all the relevant source files in some combined form?
Granted, this is not something you'd want to use during debugging of
kernel code, it would only be relevant for those trying to minimize
their kernel size and/or get the last possible bits of speed out of
the running kernel.
next prev parent reply other threads:[~2003-08-12 16:03 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-11 21:11 [2.6 patch] add an -Os config option Adrian Bunk
2003-08-11 21:19 ` Michael Buesch
2003-08-11 21:37 ` Mike Fedyk
2003-08-11 21:39 ` Christophe Saout
2003-08-11 21:41 ` Dagfinn Ilmari Mannsåker
2003-08-12 1:29 ` Gene Heskett
2003-08-12 2:51 ` Thomas Molina
2003-08-12 4:14 ` [OT] " Steven Cole
2003-08-12 15:25 ` Timothy Miller
2003-08-12 14:48 ` Gene Heskett
2003-08-12 10:11 ` Michael Buesch
2003-08-12 14:42 ` Gene Heskett
2003-08-12 1:45 ` Warren Turkal
2003-08-11 22:20 ` Russell King
2003-08-12 7:06 ` Christoph Hellwig
2003-08-12 15:43 ` Timothy Miller
2003-08-12 15:58 ` Adrian Bunk
2003-08-12 16:03 ` Kevin P. Fleming [this message]
2003-08-12 13:35 ` Alan Cox
2003-08-12 15:45 ` Joe Korty
2003-08-12 18:03 ` Timothy Miller
2003-08-12 19:43 John Bradford
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=3F390FC4.9000300@cox.net \
--to=kpfleming@cox.net \
--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;
as well as URLs for NNTP newsgroup(s).