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 …
-
-
(Note that refterm only uses read-past-end, so it only maps the buffer twice; the read-past-both case would use an additional call, but the idea is the same).
-
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.
- Show replies
New conversation -
-
-
Great, did not realize this was added, thanks!
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.