<div class="gmail_quote">Hi,</div><div class="gmail_quote">2012/1/24 Dmitrey <span dir="ltr"><<a href="mailto:dmitrey15@ukr.net">dmitrey15@ukr.net</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Required 4 GB for 64bit machine and lots of time for build to be elapsed each day is very inconvenient. Well, I can download and install compiled version, but then I have to set all paths to the files I'm working with.<br>
Maybe somewhere there are lots of C files with -O3 or like that? Can you provide a build option e.g. --without-optimization to remove those -O3, -O2 or somehow else reduce build time and memory consumption (well I see the opts<br>
<br>
PYPY_GC_MAX_DELTA=200MB pypy --jit loop_longevity=300 ./translate.py -Ojit<br>
from <a href="http://pypy.org/download.html#building-from-source" target="_blank">http://pypy.org/download.html#<u></u>building-from-source</a><br>
<br>
but they essentially increase build time).<br></blockquote><div><br></div><div>Yes, pypy takes a long time and a lot of memory to translate.</div><div>But this is not because of C files: if you look at the output,</div><div>
you'll see that the generation and compilation of C source files</div><div>is a small part of the whole process -- and memory usage is</div><div>already at its highest then.</div><div><br></div><div>To reduce translation time and memory, you can use -O2 instead of -Ojit</div>
<div>-- but of course there won't be any JIT.</div><div>That's the option I often use, because I'm primarily interested</div><div>in the correctness of the resulting interpreter, not its speed.</div><div> </div>
</div>-- <br>Amaury Forgeot d'Arc<br>