Skip to content
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

Move the wasmtime crate directories form lib/* to wasmtime-*. #57

Merged
merged 1 commit into from
Mar 20, 2019

Conversation

sunfishcode
Copy link
Member

This follows a similar change to Cranelift made here:

bytecodealliance/cranelift#660

@bnjbvr
Copy link
Member

bnjbvr commented Mar 4, 2019

Looks good on principle (AppVeyor CI is broken, but that might be unrelated), thanks!

@sunfishcode
Copy link
Member Author

Thanks!

@sunfishcode sunfishcode merged commit db0abe8 into bytecodealliance:master Mar 20, 2019
@sunfishcode sunfishcode deleted the package-dirs branch March 20, 2019 18:30
pchickey pushed a commit to pchickey/wasmtime that referenced this pull request May 12, 2023
Use the dedicated `wasi-stderr` API for stderr, instead of
`wasi-logging`.

Fixes bytecodealliance#57.
dhil referenced this pull request in wasmfx/wasmfxtime Aug 31, 2023
This PR implements naive effect forwarding:

When generating code for `resume`, we ensure that when asked to handle an effect not considered by the `resume` instruction under consideration, we simply `suspend` and let our own parent handle the unknown effect. Once resuming from that we use a back edge to the code that invokes `resume` on the current fiber (i.e., after moving up in the handler chain to find a handler, we move down in the chain back to where the original `suspend` of the unknown effect happened).

Payloads are handled as follows:
1. When moving "up", we don't need to consider payloads: They are stored in the "payload buffer" of the `VMContext` and left untouched while moving upwards in the handler chain until the right handler is found and accesses the data.
2. When moving down, we need to deal with the "tag return payloads" that were provided via `resume` or `cont.bind` further up in the chain. These payloads are stored in continuation objects directly. Before resuming into our own child, we thus swap the payload pointers of the current continuation object and the child.
frank-emrich pushed a commit to frank-emrich/wasmtime that referenced this pull request Nov 22, 2023
mooori pushed a commit to mooori/wasmtime that referenced this pull request Dec 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants