From: Adrian Bunk <bunk@stusta.de>
To: Willy Tarreau <w@1wt.eu>
Cc: Andreas Steinmetz <ast@domdv.de>,
Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org, mtosatti@redhat.com,
Mikael Pettersson <mikpe@it.uu.se>
Subject: Re: Linux 2.4.34-pre1
Date: Mon, 21 Aug 2006 03:07:44 +0200 [thread overview]
Message-ID: <20060821010744.GE11651@stusta.de> (raw)
In-Reply-To: <20060821004146.GL602@1wt.eu>
On Mon, Aug 21, 2006 at 02:41:46AM +0200, Willy Tarreau wrote:
> On Mon, Aug 21, 2006 at 02:35:49AM +0200, Adrian Bunk wrote:
> > On Sat, Aug 19, 2006 at 06:45:33AM +0200, Willy Tarreau wrote:
> > >...
> > > Sometimes it will be compilers, but not by that much. Gcc3.[34] generally
> > > produce bigger code than 2.95 at -O2, but I don't think that people in the
> > > embedded world still use 2.95 much.
> >
> > Comparing code size different gcc versions produce with -O2 is a bit
> > unfair, the size of -Os code is more important in this case.
>
> Yes, but the code produced by gcc-3.[34] -Os is so unoptimized that it's
> practically unusable for anything oocasionnaly using the CPU. I use it
> mainly for bootloaders and tools like this. On the opposite, gcc-2.95 -Os
> was still relatively well optimized, which often resulted in faster execution
> due to smaller cache footprint. And for many programs, I have relied on this
> combination.
Embedded people often care more about size than about speed.
E.g. the ARM people always use -Os (in both 2.4 and 2.6).
For people not caring that much about size, the difference of the size
of -O2 output shouldn't matter.
> Cheers,
> Willy
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2006-08-21 1:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 22:36 Linux 2.4.34-pre1 Willy Tarreau
2006-08-16 23:54 ` Adrian Bunk
2006-08-17 5:16 ` Willy Tarreau
2006-08-17 6:48 ` Arjan van de Ven
2006-08-17 8:35 ` Andreas Steinmetz
2006-08-17 8:50 ` Mikael Pettersson
2006-08-17 12:48 ` Adrian Bunk
2006-08-17 20:43 ` Willy Tarreau
2006-08-17 23:41 ` Gerd v. Egidy
2006-08-18 4:40 ` Willy Tarreau
2006-08-21 0:56 ` Adrian Bunk
2006-08-17 9:06 ` Adrian Bunk
2006-08-17 9:16 ` Andreas Steinmetz
2006-08-18 23:25 ` Adrian Bunk
2006-08-19 1:20 ` Grant Coady
2006-08-20 17:27 ` Adrian Bunk
2006-08-19 4:45 ` Willy Tarreau
2006-08-21 0:35 ` Adrian Bunk
2006-08-21 0:41 ` Willy Tarreau
2006-08-21 1:07 ` Adrian Bunk [this message]
2006-08-17 8:37 ` Willy Tarreau
2006-08-17 9:12 ` Thomas Voegtle
2006-08-18 22:48 ` Solar Designer
2006-08-18 23:11 ` Adrian Bunk
2006-08-18 23:27 ` Solar Designer
-- strict thread matches above, loose matches on Subject: below --
2006-08-17 7:57 Chris Rankin
2006-08-17 9:16 ` Thomas Backlund
2006-08-18 4:47 ` Willy Tarreau
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=20060821010744.GE11651@stusta.de \
--to=bunk@stusta.de \
--cc=arjan@infradead.org \
--cc=ast@domdv.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
--cc=mtosatti@redhat.com \
--cc=w@1wt.eu \
/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