From: Jonathan Larmour <jlarmour@redhat.com>
To: Andrew Lunn <andrew.lunn@ascom.ch>
Cc: Robin Farine <acnrf@dial.eunet.ch>, ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] ARM startup stack & C++
Date: Wed, 08 Aug 2001 09:13:00 -0000 [thread overview]
Message-ID: <3B716537.D26A1289@redhat.com> (raw)
In-Reply-To: <20010808173203.C3798@biferten.ma.tech.ascom.ch>
Andrew Lunn wrote:
> > 4) A completely different and wonderful solution?
>
> Change your static to dynamic initialisationm so it can be done in the
> context of a thread you can control the size of the stack.
5) Enable CYGSEM_LIBC_INVOKE_DEFAULT_STATIC_CONSTRUCTORS and then they are
run from the context of the thread that runs main().
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
next prev parent reply other threads:[~2001-08-08 9:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-08 8:16 Robin Farine
2001-08-08 8:32 ` Andrew Lunn
2001-08-08 9:13 ` Jonathan Larmour [this message]
2001-08-09 0:07 ` Robin Farine
2001-08-09 0:17 ` Robin Farine
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=3B716537.D26A1289@redhat.com \
--to=jlarmour@redhat.com \
--cc=acnrf@dial.eunet.ch \
--cc=andrew.lunn@ascom.ch \
--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).