public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dannysmith at users dot sourceforge dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcj/36218] [4.4 regression] libgcj causes stack overflow in jc1.exe
Date: Tue, 13 May 2008 03:53:00 -0000 [thread overview]
Message-ID: <20080513035255.19402.qmail@sourceware.org> (raw)
In-Reply-To: <bug-36218-8837@http.gcc.gnu.org/bugzilla/>
------- Comment #2 from dannysmith at users dot sourceforge dot net 2008-05-13 03:52 -------
(In reply to comment #0)
> What negative consequences does increasing the default [stack]
> allocation have?
Minimal really, for a single threaded program like jc1.exe. We are just
reserving address space not actual memory. In a multithreaded app, each thread
reserves the same amount of address space as the primary thread (by default,
but the default can be overiden), so too high a stack reserve for main thread
can limit what is available for others.
Is it possible to adjust this limit at runtime, perhaps as
> needed?
>
No, not for main thread. It is built into the program header on MS windows.
GNAT also bumps stack reserve to 32 MB for "non-tasking" apps. See
system-mingw.ads.
In old days, 32 MB was default for win32 in gnu ld.
Danny
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36218
next prev parent reply other threads:[~2008-05-13 3:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 11:02 [Bug libgcj/36218] New: " aaronavay62 at aaronwl dot com
2008-05-12 11:04 ` [Bug libgcj/36218] " aaronavay62 at aaronwl dot com
2008-05-13 3:53 ` dannysmith at users dot sourceforge dot net [this message]
2008-05-22 20:10 ` [Bug tree-optimization/36218] [4.4 regression] VRP causes stack overflow while building libgcj pinskia at gcc dot gnu dot org
2008-05-22 20:11 ` [Bug tree-optimization/36218] [4.2/4.3/4.4 " pinskia at gcc dot gnu dot org
2008-06-06 15:04 ` rguenth at gcc dot gnu dot org
2008-06-08 16:15 ` jsm28 at gcc dot gnu dot org
2008-06-08 16:38 ` jsm28 at gcc dot gnu dot org
2008-06-11 10:50 ` aph at gcc dot gnu dot org
2008-06-13 21:42 ` mmitchel at gcc dot gnu dot org
2008-06-14 6:00 ` ian at airs dot com
2008-06-14 6:28 ` aph at gcc dot gnu dot org
2008-06-14 10:02 ` dannysmith at users dot sourceforge dot net
2008-06-14 15:44 ` aaronavay62 at aaronwl dot com
2008-07-14 8:04 ` aaronavay62 at aaronwl dot com
2008-07-30 9:24 ` aph at gcc dot gnu dot org
2008-08-22 19:29 ` rguenth at gcc dot gnu dot org
2008-08-23 18:07 ` aaronavay62 at aaronwl dot com
2008-08-27 22:13 ` jsm28 at gcc dot gnu dot org
2008-09-20 15:10 ` [Bug tree-optimization/36218] [4.2/4.3 Regression] " rguenth at gcc dot gnu dot org
2008-09-20 17:33 ` brian at dessent dot net
2008-09-20 17:53 ` rguenth at gcc dot gnu dot org
2009-03-31 20:51 ` [Bug tree-optimization/36218] [4.3 " jsm28 at gcc dot gnu dot org
2009-08-04 12:40 ` rguenth at gcc dot gnu dot org
2010-05-22 18:24 ` rguenth at gcc dot gnu dot org
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=20080513035255.19402.qmail@sourceware.org \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).