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.

Sign up for GitHub

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

Jump to bottom

spawn #129

Closed
willemneal opened this issue Apr 30, 2019 · 3 comments
Closed

spawn #129

willemneal opened this issue Apr 30, 2019 · 3 comments
Labels
wasi:api Issues pertaining to the WASI API, not necessarily specific to Wasmtime.

Comments

@willemneal
Copy link

Since there is no fork/exec, is invoking another program up to the runtime?

Is there a convention for doing it such as creating a special file?
@sunfishcode sunfishcode added the wasi:api Issues pertaining to the WASI API, not necessarily specific to Wasmtime. label May 1, 2019
@sunfishcode
Copy link
Member

There is not yet a convention for doing this. It's something we'd like to add though!

kubkon pushed a commit that referenced this issue Nov 7, 2019
@kubkon
Sync with latest wasmtime rev
63c1f71 
This commit syncs tests with latest wasmtime revision.
As such, it now utilises the `wasmtime-api` crate for
runtime setup.

Closes #126, #127, #128, #129.
@bjorn3
Copy link
Contributor

bjorn3 commented Feb 3, 2021

Should this be moved to https://github.com/webassembly/wasi?

@sunfishcode
Copy link
Member

The original question is answered; if someone wants to discuss this further, opening an issue in the WASI repository would be a good starting point!

grishasobol pushed a commit to grishasobol/wasmtime that referenced this issue Nov 29, 2021
@willglynn @pepyakin
Hide instruction storage details (bytecodealliance#129)
7509477 
* Hide Instructions implementation behind an iterator

* Hide instruction encoding behind isa::Instructions::push()

* Consistently use u32 for program counter storage

* Refer to instructions by position rather than index
pchickey added a commit to pchickey/wasmtime that referenced this issue May 12, 2023
@pchickey
Remove resource abstraction from clocks (bytecodealliance#129)
e5b6452 
* wit: remove resource index from monotonic-clocks and wall-clocks, delete instance-*-clock interfaces

At this time, we don't have use cases for providing multiple wall clocks
or multiple monotonic clocks to the same component. So, according to the
principle of following preview 1's design as close as possible, we are
changing these interfaces to being provided by ambient functions, rather
than methods on a resource.

* adapter: unresourcify clocks

* host: de-resourcify clocks
pchickey added a commit to pchickey/wasmtime that referenced this issue May 16, 2023
@pchickey
Remove resource abstraction from clocks (bytecodealliance#129)
146f576 
* wit: remove resource index from monotonic-clocks and wall-clocks, delete instance-*-clock interfaces

At this time, we don't have use cases for providing multiple wall clocks
or multiple monotonic clocks to the same component. So, according to the
principle of following preview 1's design as close as possible, we are
changing these interfaces to being provided by ambient functions, rather
than methods on a resource.

* adapter: unresourcify clocks

* host: de-resourcify clocks
mooori pushed a commit to mooori/wasmtime that referenced this issue Dec 20, 2023
@akashin
Merge pull request bytecodealliance#129 from near/zkasm_scripts
2b6eeef 
Add ability to pass arguments to zkasm-result.py
frank-emrich pushed a commit to frank-emrich/wasmtime that referenced this issue Mar 15, 2024
@dhil
Merge with upstream (bytecodealliance#129)
8f8dded
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
wasi:api Issues pertaining to the WASI API, not necessarily specific to Wasmtime.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@willemneal @sunfishcode @bjorn3