From: Wolfgang Denk <wd@denx.de>
To: Gabriel Paubert <paubert@iram.es>
Cc: "Srinivas Rao.M" <msrao@vxl.co.in>,
Embedded Linux list <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: speed and space Optimization
Date: Thu, 08 Mar 2001 18:18:01 +0100 [thread overview]
Message-ID: <20010308171806.B446B281E1@denx.denx.de> (raw)
In-Reply-To: Your message of "Thu, 08 Mar 2001 15:54:16 +0100." <Pine.HPX.4.10.10103081551290.9166-100000@gra-ux1.iram.es>
In message <Pine.HPX.4.10.10103081551290.9166-100000@gra-ux1.iram.es> you wrote:
>
> Actually, the gcc code generation of PPC lacks in this area. There are
> very few differences between -O2 -Os (first one is the standard for speed
> although you might want to try -O3). -Os is in theory the space
> optimization, but there are very few places in the rs6000/ppc description
> that depend on whether the code should be optimized for space or not.
> There will be some difference, but relatively very small.
Just tested on our PPCBoot firmware:
text data bss dec hex filename ==> size
80628 22096 10476 113200 1ba30 ppcboot-Os 100%
86332 22096 10476 118904 1d078 ppcboot-O2 105%
90464 22328 10476 123268 1e184 ppcboot-O3 109%
Differences are small, but they exist (and they can make the
difference if the code fits in a 128k boot ROM or not).
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Hindsight is an exact science.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-03-08 17:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-08 13:37 Going to sleep atomically Ralph Blach
2001-03-08 14:25 ` speed and space Optimization Srinivas Rao.M
2001-03-08 14:54 ` Gabriel Paubert
2001-03-08 15:18 ` Srinivas Rao.M
2001-03-08 15:48 ` Gabriel Paubert
2001-03-08 23:47 ` Graham Stoney
2001-03-09 0:26 ` Gabriel Paubert
2001-03-08 17:18 ` Wolfgang Denk [this message]
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=20010308171806.B446B281E1@denx.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=msrao@vxl.co.in \
--cc=paubert@iram.es \
/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).