From: Andy Wingo <wingo@pobox.com>
To: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
Cc: Chapi Chapo <rixed@happyleptic.org>, 13088@debbugs.gnu.org
Subject: bug#13088: stack overflow while compiling
Date: Thu, 07 Mar 2013 14:26:51 +0100 [thread overview]
Message-ID: <87ehfribms.fsf@pobox.com> (raw)
In-Reply-To: <CAGua6m0C5LGuQ4OQ6Ox5VcH_RiLDuCfv8L214dnLAyumJ6pcng@mail.gmail.com> (Stefan Israelsson Tampe's message of "Sat, 8 Dec 2012 22:44:15 +0100")
On Sat 08 Dec 2012 22:44, Stefan Israelsson Tampe <stefan.itampe@gmail.com> writes:
> tail-call 2000+ argument function which is not supported in guile :-)
This should be supported. Just fixed this in stable-2.0.
> I suggest that we close this bug or perhaps add a feature request for
> growing stacks.
>
> An alternate feature request is to have some way to tell guile the size
> of the stack at start up.
In this case I agree, there is no bug in the expander or in the
compiler. We should be able to grow stacks, but that is tricky with
stable-2.0. Ideally we would be able to link different stack segments
together with overflow/underflow handlers, as in the Dybvig paper, but
that would require some experimentation that would best be done on
master.
I pushed a patch based on yours to add a GUILE_STACK_SIZE environment
variable. I hate environment variables but hopefully we can remove it
in 2.2.
Thanks for looking into this!
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2013-03-07 13:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 16:31 bug#13088: stack overflow while compiling rixed
2012-12-06 16:01 ` Stefan Israelsson Tampe
2012-12-08 21:44 ` Stefan Israelsson Tampe
2012-12-10 12:16 ` rixed
2012-12-11 22:29 ` Stefan Israelsson Tampe
2012-12-12 8:33 ` rixed
2012-12-12 17:13 ` Stefan Israelsson Tampe
2012-12-14 12:46 ` rixed
2013-03-07 13:27 ` Andy Wingo
2013-03-07 13:26 ` Andy Wingo [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
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=87ehfribms.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=13088@debbugs.gnu.org \
--cc=rixed@happyleptic.org \
--cc=stefan.itampe@gmail.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).