Re: Default stack limit

[Kevin Ryde]

Andy Wingo <address@hidden> 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 ...)