From: Gary Thomas <gthomas@redhat.com>
To: Andreas.Karlsson@combitechsystems.com
Cc: ecos-discuss@sourceware.cygnus.com
Subject: RE: [ECOS] Size of downloaded files?
Date: Mon, 18 Sep 2000 07:33:00 -0000 [thread overview]
Message-ID: <XFMail.20000918083253.gthomas@redhat.com> (raw)
In-Reply-To: <2253171AF143D21185A60000F8FA748B0229A971@pluto.combitech.se>
On 18-Sep-2000 Andreas.Karlsson@combitechsystems.com wrote:
> Hi,
>
> Is there any way I can see how much each .c file contributes to the size
> that will be downloaded to the target?
Yes and no. Something simple like:
find . -name "*.o" -exec arm-elf-size \{} \;
will show you the rough sizes of the object files.
However, due to selective linking this will be misleading since much
of what you might see can be left out if you're not actually using it.
You can also generate a linker map to see what sections and their sizes
are part of the final image.
next prev parent reply other threads:[~2000-09-18 7:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-18 7:13 Andreas.Karlsson
2000-09-18 7:33 ` Gary Thomas [this message]
2000-09-18 8:15 Andreas.Karlsson
2000-09-18 8:18 ` Gary Thomas
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=XFMail.20000918083253.gthomas@redhat.com \
--to=gthomas@redhat.com \
--cc=Andreas.Karlsson@combitechsystems.com \
--cc=ecos-discuss@sourceware.cygnus.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).