From: David Woodhouse <dwmw2@infradead.org>
To: Helge Hafting <helge.hafting@aitel.hist.no>
Cc: Rob Landley <rob@landley.net>,
linux-kernel@vger.kernel.org, linux-tiny@selenic.com,
devel@laptop.org
Subject: Re: [PATCH 0/4] Compile kernel with -fwhole-program --combine
Date: Mon, 28 Aug 2006 12:21:16 +0100 [thread overview]
Message-ID: <1156764076.5340.75.camel@pmac.infradead.org> (raw)
In-Reply-To: <44F2CB09.2010809@aitel.hist.no>
On Mon, 2006-08-28 at 12:52 +0200, Helge Hafting wrote:
> And a "make optImage" (optimized image) when building a
> kernel for production use, when you believe compiling every file
> and spending lots of extra time is worth it.
If we revamp the entire kbuild infrastructure to allow building the
_whole_ kernel with --combine then I might be inclined to agree -- we
could do that instead of a CONFIG_COMBINED_COMPILE option.
But if, as I suggest, we're doing the simple option which combines only
the files which tend to get most benefit from it -- those which are in
the same directory -- then there's not a lot of point in the separate
target. It really doesn't take that much extra time.
--
dwmw2
next prev parent reply other threads:[~2006-08-28 11:25 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1156429585.3012.58.camel@pmac.infradead.org>
2006-08-24 15:24 ` David Woodhouse
2006-08-24 16:48 ` Jan Engelhardt
2006-08-24 17:05 ` David Woodhouse
2006-08-25 6:01 ` Jan Engelhardt
2006-08-25 7:26 ` Sam Ravnborg
2006-08-25 10:14 ` David Woodhouse
2006-08-25 8:55 ` David Woodhouse
2006-08-25 9:11 ` Jan Engelhardt
2006-08-25 9:45 ` David Woodhouse
2006-08-25 9:51 ` Jan Engelhardt
2006-08-25 10:01 ` David Woodhouse
2006-08-24 17:15 ` [OLPC-devel] " Arnd Bergmann
2006-08-24 17:25 ` David Woodhouse
2006-08-24 21:49 ` Adrian Bunk
2006-08-24 21:54 ` David Woodhouse
2006-08-25 20:11 ` Rob Landley
2006-08-25 20:35 ` David Woodhouse
2006-08-26 1:59 ` Segher Boessenkool
2006-08-28 10:52 ` Helge Hafting
2006-08-28 11:03 ` Jan Engelhardt
2006-08-28 11:21 ` David Woodhouse [this message]
2006-09-01 19:35 ` Ian Stirling
2006-09-01 21:15 ` David Woodhouse
2006-08-24 15:25 ` [PATCH 1/4] Inconsistent extern declarations David Woodhouse
2006-08-24 16:13 ` Alexey Dobriyan
2006-08-24 17:50 ` David Woodhouse
2006-08-24 21:17 ` Adrian Bunk
2006-08-24 15:26 ` [PATCH 2/4] Core support for --combine -fwhole-program David Woodhouse
2006-08-24 17:27 ` Josh Triplett
2006-08-24 17:33 ` David Woodhouse
2006-08-24 21:33 ` Adrian Bunk
2006-08-25 9:37 ` David Woodhouse
2006-08-25 10:30 ` Adrian Bunk
2006-08-25 10:40 ` David Woodhouse
2006-08-24 15:26 ` [PATCH 3/4] Add __global tag where needed David Woodhouse
2006-08-24 21:30 ` Adrian Bunk
2006-08-25 9:52 ` David Woodhouse
2006-08-25 10:26 ` Adrian Bunk
2006-08-25 10:34 ` David Woodhouse
2006-08-25 10:50 ` Adrian Bunk
2006-08-24 15:28 ` [PATCH 4/4] Some extra --combine hacks David Woodhouse
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=1156764076.5340.75.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=devel@laptop.org \
--cc=helge.hafting@aitel.hist.no \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tiny@selenic.com \
--cc=rob@landley.net \
/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®