public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: "Lewin A.R.W. Edwards" <larwe@larwe.com>
Cc: Paul Pham <ppham@MIT.EDU>, ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Size of eCos binaries
Date: Fri, 12 Jan 2001 18:33:00 -0000	[thread overview]
Message-ID: <20010112203348.A25255@visi.com> (raw)
In-Reply-To: <4.3.2.7.2.20010112205349.00ae93e0@larwe.com>

On Fri, Jan 12, 2001 at 08:55:23PM -0500, Lewin A.R.W. Edwards wrote:
> 
> >After I built the eCos libraries for the ARM chip using the Windows
> >Configuration tool, I tried compiling the example programs (hello, serial,
> >etc.) with arm-elf-gcc and the accompanying Makefile. The resulting binaries
> >were about 1 MB large. Is this typical, or am doing something wrong?
> 
> This is normal and typical. Most of that information is debugging 
> information and ELF stuff. When you upload the binary to the target board 
> you'll see that the code size is under 128K.

If you want to see the actual sizes of things you can either use the "size"
program or the objdump program:

$ size elfFileName
$ objdump --sectionHeaders elfFileName

depending on how the tools were build, you may have to put a prefix on the
program names:

$ arm-elf-size elfFileName
$ arm-elf-objdump --sectionHeaders elfFileName

Objdump and objcopy are extremely useful programs.  They can do lots of
different handy things. Read the man pages for both of them.  Honestly, it's
worthwhile.

-- 
Grant Edwards
grante@visi.com

      reply	other threads:[~2001-01-12 18:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-12 17:13 Paul Pham
2001-01-12 17:55 ` Lewin A.R.W. Edwards
2001-01-12 18:33   ` Grant Edwards [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=20010112203348.A25255@visi.com \
    --to=grante@visi.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=larwe@larwe.com \
    --cc=ppham@MIT.EDU \
    /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).