From: Jonathan Larmour <jlarmour@redhat.com>
To: Carlos Camargo <carlos_ivan_camargo@yahoo.com>
Cc: "'ecos-discuss@sources.redhat.com'" <ecos-discuss@sources.redhat.com>
Subject: Re: [ECOS] Executable Size
Date: Thu, 31 May 2001 11:26:00 -0000 [thread overview]
Message-ID: <3B168CE4.5B540F1C@redhat.com> (raw)
In-Reply-To: <20010531174541.55072.qmail@web14001.mail.yahoo.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 935 bytes --]
Carlos Camargo wrote:
>
> text data bss dec hex filename
> 45880 1956 23544 71380 116d4 twothreads
>
> But, i don`t understand this information, when i use
> man size don´t provide information about this format
Try "info size" which is a little bit better.
But basically, text==code, and data+bss==your program data. This totals
71380 bytes in this case (rather large for such a simple case, but easily
reduced by tailoring your eCos configuration if you choose).
For a program programmed into ROM/Flash, you would find the total ROM usage
to be text+data, and the total RAM usage to be data+bss.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions http://www.redhat-techworld.com/
next prev parent reply other threads:[~2001-05-31 11:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-31 8:35 [ECOS] What is RedBoot_INIT_TAB, Narayana, Venkat A.
2001-05-31 8:54 ` Gary Thomas
2001-05-31 9:03 ` Jonathan Larmour
2001-05-31 10:02 ` [ECOS] Executable Size Carlos Camargo
2001-05-31 10:15 ` Jonathan Larmour
2001-05-31 10:45 ` Carlos Camargo
2001-05-31 11:26 ` Jonathan Larmour [this message]
2001-05-31 11:12 Dan Conti
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=3B168CE4.5B540F1C@redhat.com \
--to=jlarmour@redhat.com \
--cc=carlos_ivan_camargo@yahoo.com \
--cc=ecos-discuss@sources.redhat.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).