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
Meta: pass the testsuite #14
Comments
Closed
All of the above are now implemented on master. The spec testsuite now passes! |
That’s just awesome! Great job! |
kubkon
added a commit
to kubkon/wasmtime
that referenced
this issue
Mar 11, 2020
…> trait (bytecodealliance#14) * merge GuestTypePtr and GuestTypeClone into a single GuestTypeClone<'a> trait * GuestArray can derive Clone (but not impl GuestTypeClone) * fix array tests * Fix GuestTypeClone for flags Co-authored-by: Jakub Konka <kubkon@jakubkonka.com>
grishasobol
pushed a commit
to grishasobol/wasmtime
that referenced
this issue
Nov 29, 2021
Second iteration on documenation.
howjmay
pushed a commit
to howjmay/wasmtime
that referenced
this issue
Jan 24, 2022
Since there's no non-v0 tagged releases, go get will download the master branch, which doesn't contain the build files. Once there's a v1, this extra bit can be removed.
dhil
added a commit
to dhil/wasmtime
that referenced
this issue
Feb 27, 2023
…merge-2 Function references merge (again)
pchickey
pushed a commit
to pchickey/wasmtime
that referenced
this issue
May 12, 2023
This forces all the `*.wit.md` file to go into one large `*.wit` file for now which will get split up later once `use` is re-introduced.
pchickey
pushed a commit
to pchickey/wasmtime
that referenced
this issue
May 16, 2023
This forces all the `*.wit.md` file to go into one large `*.wit` file for now which will get split up later once `use` is re-introduced.
dhil
added a commit
to frank-emrich/wasmtime
that referenced
this issue
Sep 28, 2023
Merge with upstream
mooori
pushed a commit
to mooori/wasmtime
that referenced
this issue
Dec 20, 2023
…ack space (bytecodealliance#14) Since now we're looking at supporting an architecture with stack growth in an unusual direction, it is better to be intentional about what semantic purpose these have, and having them as separate instructions makes it somewhat easier to think about this.
mooori
pushed a commit
to mooori/wasmtime
that referenced
this issue
Dec 20, 2023
…nce#15) * zkasm: rename some types and structures away from RV64 * zkASM: remove the unwinding code * Revert "zkasm: split AdjustSp to separate variants for Reserve and Release stack space (bytecodealliance#14)" This reverts commit 0798ff7.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This will require at least these features:
call_indirect
implementation (signature checking, checking the item isn't null, etc)The text was updated successfully, but these errors were encountered: