From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: [9fans] mainstacksize
Date: Thu, 8 Aug 2002 17:05:57 +0900 [thread overview]
Message-ID: <a8e3d99cbc606cf0003761e4a7f0e50f@granite.cias.osakafu-u.ac.jp> (raw)
Theradmain prepares 8 Kbytes stack area fot it, according to the manual.
I have a program using threadmain, and from which a function having a 200x200
float array. I put this array to static memory, however, it requires more than
8 Kbytes threadmain's stack area. (When I use the array as local, it goes to more
miserabble result.)
Therefore, I enlarged the default value of the stack size of the threadmain to 30Kbytes,
and now the function works more stablly. (I'm still debugging!) Why a farely large
array put in a static/global field can be affected from the stack of the threadmain?
What's the meaning of mainstacksize of thread library?
Kenji
next reply other threads:[~2002-08-08 8:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-08 8:05 okamoto [this message]
2002-08-08 14:44 Russ Cox
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=a8e3d99cbc606cf0003761e4a7f0e50f@granite.cias.osakafu-u.ac.jp \
--to=okamoto@granite.cias.osakafu-u.ac.jp \
--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).