thanks, will try that.<br><br>(used stackless python a while back for simulation - <a href="http://amundtveit.info/publications/2003/zereal.pdf">http://amundtveit.info/publications/2003/zereal.pdf</a> )<br><br>Amund<br><br>
<br><div><span class="gmail_quote">2008/1/29, Carl Friedrich Bolz <<a href="mailto:cfbolz@gmx.de">cfbolz@gmx.de</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Amund,<br><br>Amund Tveit wrote:<br>> Hi, I wrote a blog entry yesterday about using rpython for the great<br>> computer language shootout recursive program, and got a RunTime error<br>> when I input on the commandline 11 (1 to 10 goes fine). Just did an<br>
> svn update of pypy to version 51115 and still get the error, here is<br>> the program:<br><br>The runtime error is a stack overflow. RPython is checking for stack<br>overflows when a recursive call is occuring (which is probably also the<br>
reason why the RPython version is slower). It is a bit conservative in<br>doing that, which is why C still works for 11, but not the RPython version.<br><br>To simulate an infinite stack you could additionally pass in the option<br>
stackless=True and gc="generation" instead of ="ref" to the Translation<br>class. This will make the program slightly slower, but should allow you<br>very large arguments (argument sizes that probably make the normal C<br>
version segfault).<br><br>Cheers,<br><br>Carl Friedirch<br></blockquote></div><br><br clear="all"><br>-- <br>Amund Tveit<br><a href="http://amundtveit.info/">http://amundtveit.info/</a> - +47 416 26 572