From: obry@ACT-Europe.FR (Pascal Obry)
To: binutils@sources.redhat.com, danny_r_smith_2001@yahoo.co.nz,
dj@delorie.com
Subject: binutils, why default stack size this low ?
Date: Wed, 16 Jan 2002 14:08:00 -0000 [thread overview]
Message-ID: <20020116213233.818F22264C@paris.ACT-Europe.FR> (raw)
> Larger reserves limited the number of threads you could start. The
> MSVC compiler had a much smaller reserve than Cygwin before the patch.
Right, but this has the bad consequence to break some non-threaded
programs. It was always possible to change the default stack size on the
command line. Of course this is also true for non-threaded programs, but I
think that most of the programs around us do not use threads.
Even on the Ada world, where tasking is part of the language, we have many
programs that do not use tasks (threads), and those who do does not have
enough tasks to break the limit (which is around 35 if my memory
is right).
Pascal Obry.
next reply other threads:[~2002-01-16 21:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-16 14:08 Pascal Obry [this message]
2002-01-16 20:32 ` Danny Smith
-- strict thread matches above, loose matches on Subject: below --
2002-01-16 13:32 Pascal Obry
2002-01-16 14:03 ` DJ Delorie
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=20020116213233.818F22264C@paris.ACT-Europe.FR \
--to=obry@act-europe.fr \
--cc=binutils@sources.redhat.com \
--cc=danny_r_smith_2001@yahoo.co.nz \
--cc=dj@delorie.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).