From: Andy Wingo <wingo@pobox.com>
Subject: Re: Default stack limit
Date: Wed, 10 May 2006 16:31:04 +0200 [thread overview]
Message-ID: <1147271464.23680.140.camel@localhost.localdomain> (raw)
In-Reply-To: <87bqu6kext.fsf_-_@minimini.mvo.home>
Hi,
On Wed, 2006-05-10 at 01:31 +0300, Marius Vollmer wrote:
> Andy Wingo <wingo@pobox.com> writes:
>
> > Speaking of which, a -g compile on PPC uses quite a lot of stack -- I
> > had to up the default limit in order to get anything to work (for
> > example, compiling psyntax). That would be another issue though...
>
> Yeah, it's a "known issue" also on x86. The default stack limit is a
> bit tight for a "-O0" build. I guess we should just double it or
> something. Or should we make the default 'unlimited'?
I think that 50000 words (200KB/400KB) should be more than enough for
anyone.
Haha. (Right now it is 20000 words.) Seriously, we should look into why
this is the case, has SCM had similar issues with newer GCC, etc. Is it
just the compilers that changed, or was it frames, or ...
Regards,
--
Andy Wingo
http://wingolog.org/
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-05-10 14:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-07 19:40 guile 1.8 and x86_64 Quanah Gibson-Mount
2006-04-10 8:14 ` Ludovic Courtès
2006-04-10 22:55 ` Neil Jerram
2006-04-10 23:03 ` Quanah Gibson-Mount
2006-04-11 20:37 ` Neil Jerram
2006-04-11 20:52 ` Quanah Gibson-Mount
2006-05-05 14:05 ` Miroslav Lichvar
2006-05-06 11:12 ` Miroslav Lichvar
2006-05-07 21:29 ` Marius Vollmer
2006-05-08 10:28 ` Andy Wingo
2006-05-08 21:52 ` Marius Vollmer
2006-05-09 6:49 ` Neil Jerram
2006-05-09 13:23 ` Andy Wingo
2006-05-09 22:31 ` Default stack limit Marius Vollmer
2006-05-10 14:31 ` Andy Wingo [this message]
2006-05-10 23:58 ` Kevin Ryde
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1147271464.23680.140.camel@localhost.localdomain \
--to=wingo@pobox.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).