-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Heads up: Scheduling a vote for phase 2 #25
Comments
I made a quick implementation in wasm3: https://github.com/tommie/wasm3/tree/custom-page-size tommie/wasm3@3d2dfb7 Since it's running on small devices (RP2040 for me,) having small page sizes is really useful. (That said, I made some PRs for fuzz-bugs others had found, which aren't being addressed, so I think wasm3 is about to die out.) |
Very cool! Thanks for sharing, will dig in a bit.
Yeah, my understanding is that unfortunately the war in Ukraine has severely impacted wasm3's author. Terrible. |
The vote happened and passed, so I will close this issue. |
Yes, fuzz-bugs are currently not addressed due to a lack of resources. Frankly, I have more interesting and financially rewarding tasks on my plate. At some point, Wasm3 may receive more attention and care. |
This issue is an announcement for visibility: I'm adding an agenda item to the 2024-07-30 CG meeting to give an update on the discussion in #13 and the prototype implementation status in Wasmtime as well as to vote for moving this proposal to phase 2.
As a reminder, these are the phase 2 entry requirements:
If anyone believes that that there exists a better design for supporting smaller-than-64KiB memories, that an alternative approach hasn't received enough consideration, etc... please speak up well before then! Feel free to leave a comment here, open an issue in this repo, or reach out to me privately.
The text was updated successfully, but these errors were encountered: