From: rixed@happyleptic.org
To: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
Cc: 13088@debbugs.gnu.org
Subject: bug#13088: stack overflow while compiling
Date: Mon, 10 Dec 2012 13:16:09 +0100 [thread overview]
Message-ID: <20121210121609.GA15887@securactive.lan> (raw)
In-Reply-To: <CAGua6m0C5LGuQ4OQ6Ox5VcH_RiLDuCfv8L214dnLAyumJ6pcng@mail.gmail.com>
-[ Sat, Dec 08, 2012 at 10:44:15PM +0100, Stefan Israelsson Tampe ]----
> The whole macro-expansion to tree-il in psyntax is not done in a tail call
> manner which limits the sizes
> of code tree's that we can compile. Although it would be interesting to
> know how to code the
> psyntax expand algorithm in such a way that we don't risk blowing the
> stack, I think we
> will be better served by waiting for better stack algorithm that implement
> growing stacks.
If it was not obvious already I must confess I'm ignorant about the internals
of guile (and of any other scheme compiler), so what I will say is probably
irrelevant. but I changed the cond into the equivalent if forms, which
I believe are not macros, but the result is the same (stack overflow).
> An alternate feature request is to have some way to tell guile the size of
> the stack at start up.
If though that was what '(debug-set! stack x)' was for, but this does not
seams to change anything. I also tried changing stack limits with ulimit
to no avail.
> For now anyone that need to compile large functions the only option, I
> believe, is to change the stack size in the code
> and recompile.
Any hint on how to do that specifically for guile, beyond the above
ulimit/setrlimit?
next prev parent reply other threads:[~2012-12-10 12:16 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 [this message]
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
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=20121210121609.GA15887@securactive.lan \
--to=rixed@happyleptic.org \
--cc=13088@debbugs.gnu.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).