3 ms·
Yes. It's essentially x86_64 but with all addresses being 32-bits, so you get all the things like extra registers that x86_64 added without the added memory blo
by gsnedders 8y ago
Yes. It's essentially x86_64 but with all addresses being 32-bits, so you get all the things like extra registers that x86_64 added without the added memory bloat of longer addresses for everything.
- mg794613 8y agoWhat "bloat"? It's curious to see that when a technique comes out and is being misunderstood by the masses and praised as the best thing since sliced bread. Suddenly robustness, accountability and predictability turn into "bloat". Do you have a real world example?
- tomlu 8y agoIf you double the size of pointers (64 bit, up from 32 bit) then your program will take up more heap. This is especially significant for languages where everything is a heap allocation.
- zakk 8y agoIf you code does intresive computation with structures containing a lot of pointers, you’ll get much more cache miss when using 64 but pointers. The performance hit can be quite heavy! Cache is a limited resource, and you want as many pointers as possible to fit there.
- chaosite 8y agoIt's bloat used properly, in the most literal sense. Your pointers are 64bit, but you always use less than 32bits. So, all your pointers are twice is big. This wasted space from bits you do not need is "bloat".