From: lunn@ma.tech.ascom.ch (Andrew Lunn)
To: ecos-discuss@sourceware.cygnus.com
Subject: [ECOS] stacks as globel char[]
Date: Fri, 07 May 1999 00:02:00 -0000 [thread overview]
Message-ID: <199905070702.JAA09921@biferten.ma.tech.ascom.ch> (raw)
This question comes out of ignorance as to how the compiler/loader works.
In the example code you have the stacks as a global char
stack[x][y]. Is this a good idea for real applications? The same
applies to memory for memory pools etc.
Im thinking about code that is for a ROM, or downloading over a serial
line. If i looked at this code would i find lots of zeros which are
the stack and memory for the pool, or are these variables created
during run time startup?
Thanks
Andrew
----------------------------------------------------------------------
Dr Andrew Lunn Phone: +41 62 889 5297
ASCOM Systec AG Fax: +41 62 889 5290
Gewerberpark Email: Andrew.Lunn@ascom.ch
CH-5506 Magenwil
Switzerland
----------------------------------------------------------------------
next reply other threads:[~1999-05-07 0:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-05-07 0:02 Andrew Lunn [this message]
1999-05-07 4:11 ` [ECOS] " Bart Veer
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=199905070702.JAA09921@biferten.ma.tech.ascom.ch \
--to=lunn@ma.tech.ascom.ch \
--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).