Hacker News Reader

> The stack does not grow because HolyC does not utilize virtual memory.

How does this work?

memory is identity mapped in templeos. so page faults are meaningless.

that statement is false though, because paging is mandatory in long mode. all memory accesses are virtual memory accesses.

If all memory is identity mapped, how does one program cooperate with another absent OS intervention? Can memory corruption happen when one process accidentally writes in the address space of another? What about overflows?

yes

the whole os is one address space

Reply on news.ycombinator.com