From: Tom Rini <trini@kernel.crashing.org>
To: Rob Landley <landley@trommello.org>
Cc: Bill Davidsen <davidsen@tmr.com>, Adrian Bunk <bunk@fs.tum.de>,
Rasmus Andersen <rasmus@jaquet.dk>,
linux-kernel@vger.kernel.org
Subject: Re: CONFIG_TINY
Date: Mon, 4 Nov 2002 12:51:44 -0700 [thread overview]
Message-ID: <20021104195144.GC27298@opus.bloom.county> (raw)
In-Reply-To: <200211012059.32304.landley@trommello.org>
On Mon, Nov 04, 2002 at 02:13:48AM +0000, Rob Landley wrote:
> On Friday 01 November 2002 14:15, Tom Rini wrote:
>
> > > Sure, and unrolling loops can cause cache misses and be slower than that
> > > jmp back in a loop. The point is this is a string, the people who think
> > > they're able to hand diddle the options can change it. And more to the
> > > point anyone who can't find a string in a makefile shouldn't be second
> > > guessing the compiler anyway.
> >
> > Yes, so why can't those who still need a few more kB after trying some
> > of the other options go and find '-O2' and replace it with '-Os' ?
>
> Because the point of CONFIG_TINY is to make the kernel smaller and this is
> something that makes the kernel smaller? (In fact telling the compiler
> "optimize for size" is one of the most OBVIOUS things to do?)
>
> I've used -Os. I've compiled dozens and dozens of packages with -Os. It has
> always saved at least a few bytes, I have yet to see it make something
> larger. And in the benchmarks I've done, the smaller code actually runs
> slightly faster. More of it fits in cache, you know.
Then we don't we always use -Os?
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2002-11-04 19:48 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-30 22:36 CONFIG_TINY Rasmus Andersen
2002-10-30 23:48 ` CONFIG_TINY Rik van Riel
2002-10-31 0:53 ` CONFIG_TINY Adrian Bunk
2002-10-31 1:10 ` CONFIG_TINY Tom Rini
2002-10-31 5:33 ` CONFIG_TINY Mark Mielke
2002-10-31 14:33 ` CONFIG_TINY Tom Rini
2002-10-31 16:51 ` CONFIG_TINY Mark Mielke
2002-10-31 17:04 ` CONFIG_TINY Tom Rini
2002-10-31 17:12 ` CONFIG_TINY Mark Mielke
2002-10-31 17:24 ` CONFIG_TINY Tom Rini
2002-10-31 17:49 ` CONFIG_TINY Sam Ravnborg
2002-10-31 18:11 ` CONFIG_TINY Tom Rini
2002-11-01 2:09 ` CONFIG_TINY Bill Davidsen
2002-11-01 14:12 ` CONFIG_TINY Tom Rini
2002-10-31 18:26 ` CONFIG_TINY Kent Borg
2002-10-31 18:53 ` CONFIG_TINY Tom Rini
2002-11-04 2:13 ` CONFIG_TINY Rob Landley
2002-11-04 19:50 ` CONFIG_TINY Tom Rini
2002-11-04 20:34 ` CONFIG_TINY Cort Dougan
2002-11-04 16:16 ` CONFIG_TINY Rob Landley
2002-11-04 22:30 ` CONFIG_TINY Eli Carter
2002-11-01 2:10 ` CONFIG_TINY Arnaldo Carvalho de Melo
2002-10-31 21:12 ` CONFIG_TINY Luc Van Oostenryck
2002-10-31 17:08 ` CONFIG_TINY Matt Porter
2002-10-31 16:52 ` CONFIG_TINY Bernd Petrovitsch
2002-10-31 18:43 ` CONFIG_TINY Rasmus Andersen
2002-10-31 19:15 ` CONFIG_TINY Tom Rini
2002-10-31 19:27 ` CONFIG_TINY Rasmus Andersen
2002-11-01 14:19 ` CONFIG_TINY Tom Rini
2002-10-31 23:30 ` CONFIG_TINY Bernd Petrovitsch
2002-11-01 6:17 ` CONFIG_TINY Rasmus Andersen
2002-11-01 22:05 ` CONFIG_TINY Bernd Petrovitsch
2002-11-01 22:10 ` CONFIG_TINY Rasmus Andersen
2002-11-01 2:03 ` CONFIG_TINY Bill Davidsen
2002-11-01 14:15 ` CONFIG_TINY Tom Rini
2002-11-04 2:13 ` CONFIG_TINY Rob Landley
2002-11-04 19:51 ` Tom Rini [this message]
2002-11-04 16:09 ` CONFIG_TINY Rob Landley
2002-11-05 19:26 ` CONFIG_TINY Bill Davidsen
2002-11-05 19:56 ` CONFIG_TINY Tom Rini
2002-11-05 17:55 ` CONFIG_TINY Rob Landley
2002-11-06 2:05 ` CONFIG_TINY Tom Rini
2002-11-06 14:35 ` CONFIG_TINY Bill Davidsen
2002-11-05 19:59 ` CONFIG_TINY Alan Cox
2002-10-31 8:24 ` CONFIG_TINY Rasmus Andersen
2002-10-31 10:05 ` CONFIG_TINY Erik Andersen
2002-10-31 10:08 ` CONFIG_TINY Rasmus Andersen
2002-10-31 11:08 ` CONFIG_TINY Erik Andersen
2002-10-31 19:33 ` CONFIG_TINY Daniel Egger
2002-10-31 19:55 ` CONFIG_TINY Rasmus Andersen
2002-10-31 8:32 ` CONFIG_TINY Jens Axboe
2002-10-31 8:53 ` CONFIG_TINY Rasmus Andersen
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=20021104195144.GC27298@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=bunk@fs.tum.de \
--cc=davidsen@tmr.com \
--cc=landley@trommello.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rasmus@jaquet.dk \
/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®