From: Gary Thomas <gthomas@redhat.com>
To: Marco Monguzzi <marco@sitek.it>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: RE: [ECOS] dinamic memorry allocation
Date: Sat, 24 Jun 2000 05:38:00 -0000 [thread overview]
Message-ID: <XFMail.000624063756.gthomas@redhat.com> (raw)
In-Reply-To: <NCBBKIOHEKNFDFBEBPNHAEJJDNAA.marco@sitek.it>
On 24-Jun-00 Marco Monguzzi wrote:
> Hello all.
>
> Dealing with dynamic memory allocation, I noticed that the space to support
> the LIBC
> calls like malloc, calloc etc, is allocated in the .data segment. This means
> the space
> required to store the system/apps in EPROM is proportional to
> CYGPKG_NET_MEM_USAGE.
> Is it correct or there is a way to avoid that?
>
The memory used for malloc() and friends is in BSS, not DATA. This is not
held in ROM, but only exists in RAM when the application is running.
next prev parent reply other threads:[~2000-06-24 5:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-24 3:22 Marco Monguzzi
2000-06-24 5:38 ` Gary Thomas [this message]
2000-06-25 11:57 ` [ECOS] dinamic memory allocation Marco Monguzzi
2000-06-25 12:01 ` Jonathan Larmour
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.000624063756.gthomas@redhat.com \
--to=gthomas@redhat.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=marco@sitek.it \
/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).