unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: Default stack limit
Date: Thu, 11 May 2006 09:58:22 +1000	[thread overview]
Message-ID: <87psil5t5t.fsf@zip.com.au> (raw)
In-Reply-To: <1147271464.23680.140.camel@localhost.localdomain> (Andy Wingo's message of "Wed, 10 May 2006 16:31:04 +0200")

Andy Wingo <wingo@pobox.com> writes:
>
> Is it just the compilers that changed,

Seems to be, it's still fine with for instance gcc 2.95 unoptimized.

gcc 4 seems to use up a lot more stack in CEVAL()/DEVAL() when
unoptimized, something like 900 bytes for me, but why that's so I
couldn't tell.  (Keeping stack usage in that func to a minimum would
probably be a good thing in general though, as the main recursion when
interpreting ...)


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel


      reply	other threads:[~2006-05-10 23:58 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
2006-05-10 23:58                           ` Kevin Ryde [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=87psil5t5t.fsf@zip.com.au \
    --to=user42@zip.com.au \
    --cc=guile-devel@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).