One of the Unity developers raised some important points about WASM's memory model in a github thread. I contributed some additional thoughts here:https://github.com/WebAssembly/design/issues/1397#issuecomment-926119051 …
-
-
Replying to @cmuratori
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).
1 reply 0 retweets 2 likes
Replying to @EricLasota
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
0 replies
1 retweet
13 likes
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.