xaviermiller wrote:I am not sure X32 is better than x86_64 (amd64). I am not sure that everything has been adapted for x32, so you will end up with unoptimal code (in C in place of assembler) especially for multimedia applications.
My instinctive reaction to that is: so adapt that tiny percentage of libs where it matters, which would be worth community effort.
I accept that's not so useful for your average end-user, but then I don't think any Gentoo admin is an average end-user; and there aren't that many core multimedia libs using asm, though they should ofc be higher-priority than much else apart from toolchain, since they are so critical to the end-user experience.
So while I agree with your overall recommendation, as a default response, on a deeper level Gentoo users tend to be the ones making things work in unusual situations, by comparison to most distros.
The place used by code is really small compared to your data, don't focus on that.
Yes it is, but this is all about the amount of space the
data uses, not the code.
edit: it's also about having more registers and a decent ABI.
If you have > 2 Go, go for true 64 bits. And for less, you chose.
My choice is : 64 bits processor => 64 bits os.
Yeah though x32 requires an amd64 kernel, so we're talking 64-bit O/S already.
For avoidance of any doubt, I agree with you, and have always run full amd64 for the expanded address space. However I'd rather see that confined to kernel, as in it has a 4G x 32-bit space to place programs in, whereas the vast majority of programs don't need to have a 64-bit VM space of their own.
Not that I think x32 is ready; just that Gentoo experimenters are likely to be some of the people helping to get it ready, and that's good.