public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: Suet Fei Li <suetfei@bwrc.eecs.berkeley.edu>
Cc: "'ecos-discuss@sourceware.cygnus.com'"
	<ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] code size
Date: Wed, 31 Jan 2001 21:36:00 -0000	[thread overview]
Message-ID: <3A78F5E2.2F7DEE90@redhat.com> (raw)
In-Reply-To: <711F6B80B5B4D211BA900090272AB7649DB52A@noyce.eecs.berkeley.edu>

Suet Fei Li wrote:
> 
> Hi guys, I wrote an application using ecos as the OS. The total code size is
> 33K (it is for ARM). The application takes 8K. I would like to know how I
> can reduce the total code size, like what sort of configurable options I
> should use. I am directly calling the ecos kernels in my application, and
> the scheduler is a multi-queue one.
> 
> Any input will be greatly appreciated.

Difficult to tell without looking at the detail. But you may want to do an
arm-elf-objdump --syms to see where the space is going.

Make sure you remove unnecessary packages from your configuration. In
particular, disable device drivers if you don't use them. Make sure you are
using selective linking by compiling everything (including your
application) with -ffunction-sections -fdata-sections, and linking with
-Wl,--gc-sections.

For what it's worth, you should be able to reduce the size a lot from 33K.

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

  reply	other threads:[~2001-01-31 21:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-31 20:51 Suet Fei Li
2001-01-31 21:36 ` Jonathan Larmour [this message]
     [not found] <711F6B80B5B4D211BA900090272AB7649DB52B@noyce.eecs.berkeley.edu>
2001-01-31 22:11 ` Jonathan Larmour
2001-02-01  2:01   ` Jesper Skov

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=3A78F5E2.2F7DEE90@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=suetfei@bwrc.eecs.berkeley.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).