From: pkurpis@keck.hawaii.edu (Peter Kurpis)
To: ccroswhite@get2chip.com
Cc: gcc-help@gcc.gnu.org
Subject: Re: help with shriking binary size
Date: Wed, 11 Sep 2002 16:16:00 -0000 [thread overview]
Message-ID: <200209112315.NAA03585@kalani.keck.hawaii.edu> (raw)
> From gcc-help-return-10062-pkurpis=keck.hawaii.edu@gcc.gnu.org Wed Sep 11 13:06:35 2002
> I need some help. I have been running some comparisons with 2.95.3 and
> 3.2 and found that with the same machine and same source code, 3.2
> produces code that is larger by 25%-51% larger with no run time
> improvement (tested across several executables and test cases). Is
> there a way to shrink the size down to the same level as 2.95.3? Here
> are several cases:
>
> 2.95.3 3.2
> (-g):30560264 6246679(+51%)
> (-O):8889831 11198086(+26%)
> (-O2):8893383 11458534(+29%)
> (-O3):9009271 11252525(+25%)
Are these just binary sizes from ls , or segment sizes from size ? I am
not an expert, but this could be just the symbol table getting larger.
Also, you could try strip on the executables.
Second, are you using the same optimization settings? This would be a
factor, I would think...
next reply other threads:[~2002-09-11 23:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-11 16:16 Peter Kurpis [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-11 16:06 Chris Croswhite
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=200209112315.NAA03585@kalani.keck.hawaii.edu \
--to=pkurpis@keck.hawaii.edu \
--cc=ccroswhite@get2chip.com \
--cc=gcc-help@gcc.gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).