From: Peter Barada <pbarada@mail.wm.sps.mot.com>
To: dkorn@pixelpower.com
Cc: pierre.saucourt-harmel@motorola.com, crossgcc@sourceware.cygnus.com
Subject: Re: Build a short executable
Date: Sun, 01 Apr 2001 00:00:00 -0000 [thread overview]
Message-ID: <200101091706.MAA06423@hyper.wm.sps.mot.com> (raw)
Message-ID: <20010401000000.WiCUmpuflg0-WapPuMm-hwtrZpdQBXVJOr8s4X7RX9s@z> (raw)
In-Reply-To: <718D38CAB6E0D011B2C90060970C28A5642589@EXCHANGESERVER>
>>I removed the -g option to generate the cross libraries
>>(libg.a and libgcc.a) but not for my small files. I used -o2
>>everywhere and I obtained an executable file of 132656 bytes !
>
> Did you try using the 'strip' command from binutils on the output ? You'd
>be surprised how much difference it might make. It will be the main reason
>why your exe is so large.
>
Instead of strip, look at it with 'objdump --section-headers'
<foo.elf>. This will tell you the size of each of the sections in the
executable(and where they are loaded) without losing any of the
symbols from the executable.
--
Peter Barada Peter.Barada@motorola.com
Wizard 781-852-2768 (direct)
WaveMark Solutions(wholly owned by Motorola) 781-270-0193 (fax)
------
Want more information? See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~2001-04-01 0:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-09 8:17 David Korn
2001-01-09 9:07 ` Peter Barada [this message]
2001-01-10 2:16 ` Pierre Saucourt-Harmel (r54698)
2001-01-11 5:37 ` Pierre Saucourt-Harmel (r54698)
2001-04-01 0:00 ` Pierre Saucourt-Harmel (r54698)
2001-04-01 0:00 ` Pierre Saucourt-Harmel (r54698)
2001-04-01 0:00 ` Peter Barada
2001-04-01 0:00 ` David Korn
-- strict thread matches above, loose matches on Subject: below --
2001-01-09 8:05 Pierre Saucourt-Harmel (r54698)
2001-04-01 0:00 ` Pierre Saucourt-Harmel (r54698)
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=200101091706.MAA06423@hyper.wm.sps.mot.com \
--to=pbarada@mail.wm.sps.mot.com \
--cc=crossgcc@sourceware.cygnus.com \
--cc=dkorn@pixelpower.com \
--cc=pierre.saucourt-harmel@motorola.com \
/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).