3 ms·
Should be trivial to implement using ptmalloc/dlmalloc/whatevermalloc and constraining it to 4GiB. Main issue I see is that this requires a new ABI for passing
by Vogtinator 8y ago
Should be trivial to implement using ptmalloc/dlmalloc/whatevermalloc and constraining it to 4GiB.
Main issue I see is that this requires a new ABI for passing pointers around.
- adrianratnapala 8y ago> new ABI for passing pointers around. Isn't that what x32 actually is? I mean it's not just for passing pointers around. Aaaand that's the point. With x32, people who care about these sizes can use the x32 ABI which is consistent in its own way. While everyone else uses the x64 ABI. Without x32, people who want to have 32-bit pointers need to reintroduce the NEAR/FAR distinction into the source-level-APIs. Ouch. I'm guessing the real rationale for getting rid of x32 is that 32-bit pointers are just not a big enough use case to justify it.