Hi Matti, >Are you using 64-bit windows? Then using the editbin /largeaddressaware trick >as mentioned on the windows build >page you should be able to access all your >memory from the 32-bit python executable used for translation.
yes I'm on windows 64 ( win 10/64 ) and I did, but to no avail ( btw pypy builds with largeaddressaware flag too - so it is there either way ) so the memory error appears in spite of having /largeaddressaware trick, Regards Sergey On Sat, Apr 8, 2017 at 9:53 PM, Matti Picus <matti.pi...@gmail.com> wrote: > On 08/04/17 19:26, Sergey Kurdakov wrote: > >> while compiling pypy lack of memory is an issue even on machines with >> more memory that required for compilation. >> >> Basically pypy will crash when achieves 2 Gb memory limit even with >> setting pypy to use extended memory >> I suppose it starts to interfere with system memory addresses which >> are located exactly at 2 Gb starting point, > > Are you using 64-bit windows? Then using the editbin /largeaddressaware > trick as mentioned on the windows build page you should be able to access > all your memory from the 32-bit python executable used for translation. > Matti _______________________________________________ pypy-dev mailing list pypy-dev@python.org https://mail.python.org/mailman/listinfo/pypy-dev
