From: Sape Mullender <sape@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] how do you determine stacksize?
Date: Mon, 10 Nov 2003 09:24:40 -0500 [thread overview]
Message-ID: <c9ba889e48c5f9f92ed1c98a2fbded9e@plan9.bell-labs.com> (raw)
In-Reply-To: <af27090d17900da7e7413e960d6b17bd@vitanuova.com>
> i'd have thought the linker would be in a good position
> to make a good assessment of the stack requirements.
Maybe, but recursive programs will have unpredictable
calling depths.
If you don't use local arrays, 4K is almost always enough.
Sape
prev parent reply other threads:[~2003-11-10 14:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-07 23:52 Fco.J.Ballesteros
2003-11-10 12:14 ` David Presotto
2003-11-10 14:20 ` rog
2003-11-10 14:24 ` Sape Mullender [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=c9ba889e48c5f9f92ed1c98a2fbded9e@plan9.bell-labs.com \
--to=sape@plan9.bell-labs.com \
--cc=9fans@cse.psu.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 NNTP newsgroup(s).