I think there is more utility in 128-bit ALUs than 128-bit pointers, as a practical matter.
I think there is more utility in 128-bit ALUs than 128-bit pointers, as a practical matter.
Still, I don't think anyone nowadays would settle for a non-power-of-2 machine word size, even if just for backwards compatibility and even if a pointer is limited to e.g. 72 bits out of all 128. If that is the case, then another use could be a "fat pointer" that was proposed somewhere in the C world to avoid passing raw pointers without their lengths.You could pass a length of an array along with its address as long as the length of your array can fit in e.g. 56 bits, which would be enough for most use cases if we feel like going into the "640kB is enough for everyone" route again.
So far I never used mmap (no usecase that pushed me to find alternatives for the usual open&seek), but I was always curious about it.
Your statement made me search & find this ( https://unix.stackexchange.com/questions/474926/how-does-mem... ) => interesting.
Thanks :)
https://stackoverflow.com/questions/45972/mmap-vs-reading-bl...