https://www.gnu.org/software/libc/manual/html_node/Reserved-...
24 karma · joined May 17, 2011
https://www.gnu.org/software/libc/manual/html_node/Reserved-...
If you set a breakpoint in say a win32 fiber switch, and look at the disassembly, it jumps to an internal function that just saves all the registers (and flags) to the active context and restores all the registers from the resumed context every time. Don't know how more optimal that can be for the general case.
With static memory techniques you can "prove" the system has enough memory to work in all modes, i.e. device consumes 20 readings per second, keeps them in a ring buffer backed by a static fixed array, that buffer is large enough to satisfy processing rate.
>> Most of the memory used by programs are pointers
This is a huge generalization, may I add.
Yes, I will not argue that cache usage is less efficient, but I am sure you know that register access is faster than cache access, and we double the amount of registers in x64.
Furthermore, the 4GB limit does not just concern physical RAM, it also applies elsewhere, like memory mapped files.
In general, it is unlikely that you will see poorer performance from 64-bit code compared to its 32-bit counterpart.
This is actually not true. They started as a way to transfer money or IOUs between palm pilots. The web portion of the product got so much more traction that they pivoted.