4 ms·
What does Goose change about memory management ?
by MiroslavPokorny 1mo ago
What does Goose change about memory management ?
- bobbydigitales 1mo ago[dead]
- kenferry 1mo agoA lot - title could probably use editing. The language has no heap, only stack memory, so the only deallocation is returning from a call stack frame.
- yndoendo 1mo agoHow big is the stack? Too often large data will blow the top and destroy adjacent stacks in multi-thread environments. Are memory barrier fences used to check against overflow?
- gcoakes 1mo agoI think it is supposed to be stacks in the general sense of the data structure, not the literal `sp` register. I imagine they could be arbitrarily sized up to physical limits if you do some mmap magic. I'm still a bit fuzzy about how you could make useful programs with that, but it seems interesting.
- MiroslavPokorny 1mo agoStack allocations will be lost when the enclosing call exits. How does this help for long term values ?
- bobbydigitales 1mo ago[dead]
- zamalek 1mo agoIf I am reading it correctly, the compiler creates N bump allocators per function (or possibly globally) - where N is (I'm guessing at this point) determined by liveness or similar.
- deleted 1mo ago[deleted]