Re: Default stack limit

2006-05-10 Thread Kevin Ryde
Andy Wingo <[EMAIL PROTECTED]> 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. (

Re: Default stack limit

2006-05-10 Thread Andy Wingo
piling 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'?

Default stack limit

2006-05-09 Thread Marius Vollmer
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'? -- GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405