Interesting stuff
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Regarding circular ring buffer mapping, I think this is not even 100% guaranteed to work on Windows, or did something change in that regard?
-
To improve on my wording: it is subject to race conditions as far as I'm aware, but you can usually get what you want by retrying often enough. It's just that the Win32 API doesn't provide a way to map both parts atomically, unless they added an API recently.
- Show replies
New conversation -
-
-
100% agree here. And also think that what you wrote could be a good introduction to modern (64 bit systems) low-level memory management layer for games.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
"there are calls available that will map committed virtual pages to actual physical pages in bulk" Is there a way to do this on Windows?
-
Yes, there are two ways - one obvious and one not obvious :)
- Show replies
New conversation -
-
-
I enjoyed ready this thread
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I don't think this is really a problem for stack frames. You can solve the stack frame problem by just using chained memory regions instead of a single region and having 2 stack pointers (current+caller).
-
Chaining the memory regions does not "solve" the problem, because it is literally the chaining which is the problem. The point of modern 64-bit address spaces is that you no longer have to do this, because the CPU does it for you. I explained all this in detail in the post:pic.twitter.com/NgkdYb6Bgd
End of conversation
New conversation -
-
-
Didn't know you were interested in WASM. Do you think it is worth spending time learning it? Too early? Too crap?
-
WASM is great in ways, yet it’s lineage is JS (that was a hack initially), then Asm.JS (that was a clever hack upon it to solve a problem and force browser vendors hand to support it) that then was built to be backwards compatible with the previous 2 hacks (to force buy-in)
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.