| |||||||||||||
That way lies madnessThat way lies madnessPosted Sep 3, 2011 11:50 UTC (Sat) by raven667 (subscriber, #5198)In reply to: That way lies madness by dlang Parent article: The x32 system call ABI
I kind of wish that the Linux distros took that approach when transitioning to x86_64, I am of the opinion that the transition would have been a lot smoother especially for desktops had that been the case.
(Log in to post comments)
That way lies madness Posted Sep 3, 2011 17:12 UTC (Sat) by dlang (✭ supporter ✭, #313) [Link]
there were two big factors that cause distros to go the direction they did for AMD64
1. especially early on there were problems with the compatibility mode causing occasional 'strange' errors when running 32 bit userspace on a 64 bit kernel.
2. the added registers of 64 bit mode significantly improve the performance of 64 bit code vs 32 bit code, in almost every case even when you take into account the extra overhead of the larger pointers.
That way lies madness Posted Sep 6, 2011 3:30 UTC (Tue) by butlerm (subscriber, #13312) [Link]
Isn't this likely to be superior enough to motivate desktop distributions to switch to an x32 user space with a 64 bit kernel, with x86-64 libraries as extensions for those applications that actually benefit from a large address space?
|
|||||||||||||