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 …
-
-
A bit of a tangent (maybe). I don't know if this is worthwhile, but does anyone do a VM-backed ring buffer that doesn't double? If you can bound the maximum read size (this seems very possible often?) then you just need to double-map the # max read bytes at the relevant ends.
-
Don't know. I'm not sure why you would bother not mapping the whole thing, since the address space is cheap on 64-bit? Unless I'm missing your point...
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.