3 ms·
100% agreed, but I'm not so convinced it needs (much) kernel support (as per my other comment). I don't usually use much libc, so an -m32 that still made elf-x8
by geocar 8y ago
100% agreed, but I'm not so convinced it needs (much) kernel support (as per my other comment). I don't usually use much libc, so an -m32 that still made elf-x86_64 would probably be enough for me.
It is absolutely idiotic to have 64-bit pointers when I compile a program that uses less than 4 gigabytes of RAM. When such pointer values appear inside a struct, they not only waste half the memory, they effectively throw away half of the cache. -Knuth
- 0x0 8y agoI dunno, having a large address space could be useful if you work with large or lots of memory mapped files?
- AstralStorm 8y agoOr you could use large file support and not mmap everything. It is probably faster too and puts less pressure on overcommit mechanism.
- Hello71 8y agofile-backed mmap is by definition not related to overcommit, because the memory is committed by the file.
- geocar 8y agoSure. Parts of my (multi-process) application can use 64-bit pointers and parts can use 32-bit.