>> Someone on Parabola Hackers (cc:ed, but please remove it when replying to >> avoid cross-post issues) mentioned that n64 would be good (at least to have >> available somewhere) so more virtual memory could be used - the use case he >> gave was that compiling and debugging some things requires more RAM then >> can be achieved with current hardware + n32-limited virtual memory.
n64 would be good for building WebKit with debug symbols on a machine with more than 2 GiB of RAM, since ld needs more than 2 GiB of virtual memory to link it unless using special options, documented as making the link slower (it takes many minutes on a YeeLoong, since it uses much swap). >> I think he actually had a chicken-and-egg scenario where he couldn't >> compile 64-bit binutils because of memory limits. There are unrelated difficulties with cross building Parabola's toolchain for other architectures/ABIs. > And recently, the firefox people had problems building firefox in a 32-bit > address space. > http://news.softpedia.com/news/Firefox-Source-Code-Is-So-Big-It-Hit-the-32-Bit-Virtual-Address-Space-Limit-240112.shtml They have a gigabyte more of virtual memory, although it's not surprising that two different browser-like projects have such problems.
pgpdBF6fJ1obQ.pgp
Description: PGP signature
