public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Szentirmai Gergely <reg@t-online.hu>
To: Gary Thomas <gary@mlbassoc.com>,
	  eCos Discuss <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] Stack usage measurement
Date: Tue, 21 Apr 2009 08:08:00 -0000	[thread overview]
Message-ID: <49EC6419.7070108@t-online.hu> (raw)
In-Reply-To: <49EC4C8A.6040108@mlbassoc.com>



Gary Thomas írta:
> Ross Younger wrote:
>> Szentirmai Gergely wrote:
>>> Does anybody has a estimation about the stack usage of pintf stuff? [...]
>>> As a summary, I would have to avoid the usage of any printf if I'm short
>>> of memory?
>> printf (or, more precisely, the actual format conversion in vfnprintf) is
>> really quite a complicated function. This regularly bites people on limited
>> targets; sometimes simply using printf is enough to cause your application
>> to fail to link because it won't fit into RAM.
>>
>> If you don't need to print out floating point numbers, you might save a
>> little code size by disabling that support in your eCos config. Otherwise,
>> puts and putc are pretty lean and mean - you could save a lot of code and
>> stack if you can avoid printf in your application.
> 
> Good points, but 'diag_printf()' is already quite stripped; no floating point.
> 

Thank you for your suggestions. I'll keep them in my mind.

Best wishes!
Gergely

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

      reply	other threads:[~2009-04-20 12:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-19 19:28 Szentirmai Gergely
2009-04-20  8:39 ` Gary Thomas
2009-04-20 10:09   ` Szentirmai Gergely
2009-04-20 10:21     ` Ross Younger
2009-04-20 10:52       ` Gary Thomas
2009-04-21  8:08         ` Szentirmai Gergely [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=49EC6419.7070108@t-online.hu \
    --to=reg@t-online.hu \
    --cc=ecos-discuss@ecos.sourceware.org \
    --cc=gary@mlbassoc.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).