pharo-vm
pharo-vm copied to clipboard
Memory Map
The memory map should be more predictable to allow us to load segments and areas without pointer realloc. Also, we need to identify the idea of memory Area (by use, e.g. young space, code zone, stack) and do it independent of the physical layout (segments) and the interaction with the OS (sharing / caching, read only).
We need to do that the simulator works in the same way as the C code.