4 ms·
Its not like 32 bit applications are more efficient than 64 bit applications. There is place for 32 bit applications but not here! The job of a program is to d
by mritun 8y ago
Its not like 32 bit applications are more efficient than 64 bit applications.
There is place for 32 bit applications but not here! The job of a program is to do what it is supposed to do efficiently and get out of the way, and it better use all registers and instructions needed to do it.
- jodrellblank 8y agoIts not like 32 bit applications are more efficient than 64 bit applications. Yeah it is. You need to move 7 bits through memory and through the CPU, is it more efficient to pad it with 25 blank bits and move 32 bits overall, or pad with 57 blank bits and move 64 bits overall? Which is doing things "more efficiently" and "better using" the hardware?
- y4mi 8y agothats not the question you have to ask though. your cpus arent capable of 32 bit calculations anymore... so the questions is: is the software emulation of your OS for 32 bit more efficient than the programming language overprovisions.
- zaarn 8y agoThe CPU is still perfectly capable of 32bit calculations. Even 8 bit calculations. What you can't do is use 32bit pointers (though, strictly, you can, but x86-32 isn't well supported, I wonder why?)
- y4mi 8y agoYou are technically right, but only because I expressed myself very poorly. The CPU is naturally still able to do 32 bit calculations. What you can't do is run a 32 bit application without emulation after a 64 bit system has booted. The libraries are obviously also required, but it still won't be able to start without the emulation adding 0 to the memory blocks.
- Shikadi 8y agoSource? Not that I don't believe you, I just don't understand from your comment
- SIXTWOSIX 8y agoIt's not -entirely- true but it's not false, either as far as I'm aware. Windows in specific uses WOW64 -- Windows 32 on Windows 64. It's an emulation layer that doesn't actually hamper performance but does do things a bit differently than a native OS -- such as running all 32bit programs in 'user mode' rathe than with elevated permissions. You can get a brief synopsis here - https://www.techsupportalert.com/content/how-windows7-vista64-support-32bit-applications.htm https://www.techsupportalert.com/content/how-windows7-vista6...
- zaarn 8y agoIf you use eax instead of rax, you can do both. Compilers are smart these days and will use the appropriate register size when necessary. If you need to move 7 bits, it'll likely use the al register.
- jodrellblank 8y agoI can't edit, but it seems my reasons for thinking 32-bit can be faster aren't entirely daft - but the gains of 64-bit x64 include it having simply more registers, having smaller faster floating point precision, being able to request more memory at once, and the hits to pointer size overheads or processor cache holding less real data are rare and mostly from buggy or odd conditions, and that for a lot of normal programs there'll be no difference either way: https://stackoverflow.com/questions/2378399/are-64-bit-programs-bigger-and-faster-than-32-bit-versions https://stackoverflow.com/questions/2378399/are-64-bit-progr... https://stackoverflow.com/questions/324015/supplying-64-bit-specific-versions-of-your-software https://stackoverflow.com/questions/324015/supplying-64-bit-... https://stackoverflow.com/questions/2334148/is-there-any-real-point-compiling-a-windows-application-as-64-bit https://stackoverflow.com/questions/2334148/is-there-any-rea... interesting.