News for hackers. Stuff that matters.

A comment on Do Not Use Go for 32bit Development. Parent comment

Re:Do Not Use Go for 32bit Development by Mavrik on Sunday April 08, 2012 @02:17PM (#3814429)
You mean the identical limit that also 32-bit Linux applications on x86 have without reconfiguring kernel for different split?

It seems Windows bashing without any background knowledge is becoming popular again -_-

[ Parent | on HN ]
Re:Do Not Use Go for 32bit Development by someCTO on Sunday April 08, 2012 @02:39PM (#3814498)
Running a PAE kernel on 32 bit is pretty standard at this point, I believe. Please correct me if I missed something.
[ Parent | on HN ]
Re:Do Not Use Go for 32bit Development by yuhong on Sunday April 08, 2012 @03:15PM (#3814615)
It has nothing to do with PAE, but 3G/1G split I think is default on Linux.
[ Parent | on HN ]
Re:Do Not Use Go for 32bit Development by someCTO on Sunday April 08, 2012 @05:14PM (#3814931)
That does not address the 512MB of virtual address problem, which is not an issue with PAE.
[ Parent | on HN ]
Re:Do Not Use Go for 32bit Development by 4ad on Monday April 09, 2012 @06:56AM (#3816454)
Yes it is because PAE doesn't change the address space of processes. PAE let's you use more physical memory, the address space of each process is still the same, because 2^32 is still 2^32 with PAE.
[ Parent | on HN ]