Re: Bypassing the 2/3/4GB virtual memory space on 32-bit ports

> Your entire argument is built on the premis that it is actually
> desirable for these applications (compilers, linkers, etc) to work in
> 32-bit address spaces.

Why wouldn't it?

Of all my machines (2x BananaPi, 1x mac-mini, 1x T60, 1x T61, 1x X201s,
1x desktop PC) only 3 can take more than 3GB of memory and only 1 can
take more than 8GB (more specifically, it can take upto 16GB).

Am I supposed to throw away that hardware and go buy something new every
few years just because people can't be bothered to fix their
compilation-performance bugs?  Sounds like an ecological disaster to me.


        Stefan


PS: The BananaPi's 1GB was sufficient to Git-clone and recompile Debian's
kernel last year, without any need to tweak options.
Why should other programs fare so much worse?
I'd simply consider it a bug if a program needs more than 2GB
to compile.