Add Memory64 post #192
Add Memory64 post #192
Conversation
There was a problem hiding this comment.
Looks good!
One meta comment here, it would be really nice if we could quantify 'slow' somehow.
Here's several things I found online:
WebAssembly/memory64#3 (comment)
WebAssembly/memory64#3 (comment)
https://x.com/ThaLobsta/status/1332814463418810369
I also know that V8 now implements a hybrid signal-handling + bounds check scheme that gave them good results. https://groups.google.com/g/v8-reviews/c/VdlZacHKm_4
Basically do a bounds check to see if high bits are set (which requires no loading of a memory bound), then rely on a 16GiB of mapped pages.
The overall gist is still correct and worth sharing, it'd just be nice to just give them some data so they can make the informed choice.
|
Thanks for the feedback - I'll do a round of updates tomorrow and then maybe we can publish later in the day or Thursday. |
|
I'm ready to go when you all are. |
No description provided.