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 WASI discussions and close existing tickets #104

Closed
npmccallum opened this issue Apr 12, 2019 · 1 comment
Closed

Move WASI discussions and close existing tickets #104

npmccallum opened this issue Apr 12, 2019 · 1 comment
Labels
wasi:api Issues pertaining to the WASI API, not necessarily specific to Wasmtime.

Comments

@npmccallum
Copy link
Member

WASI discussions that started here should be moved to here and closed. This way we don't loose track of discussions.

@sunfishcode sunfishcode added the wasi:api Issues pertaining to the WASI API, not necessarily specific to Wasmtime. label Apr 24, 2019
@bjorn3
Copy link
Contributor

bjorn3 commented Nov 8, 2019

Closed wrong issue in PR?

grishasobol pushed a commit to grishasobol/wasmtime that referenced this issue Nov 29, 2021
…ealliance#104)

This works under the assumption that these values
are represented as an `I32` in WASM, which seems
reasonable.
howjmay pushed a commit to howjmay/wasmtime that referenced this issue Jan 24, 2022
pchickey added a commit to pchickey/wasmtime that referenced this issue May 12, 2023
* rename host runtime tests to command tests

* add a test for using wasi in a reactor

* commit cargo.lock

* reactor tests: fix wit deps

* test-programs: reactor-tests can build on stable

note that this fails because it exposes wasi-libc ctors calling import
functions from inside cabi_realloc

* test-programs: show that ctors fix in wit-bindgen fixes bug

* ci: install wasm32 targets for stable as well as nightly

* wit-bindgen: use 0.4.0

* ci: use wit-bindgen 0.4.0

* Co-habitate with wasi-common from wasmtime

* adapter: code motion in cargo feature & artifact names to cli-command, cli-reactor

there will shortly be a third type of reactor (non-cli, idk what to call it)

---------

Co-authored-by: Trevor Elliott <telliott@fastly.com>
pchickey added a commit to pchickey/wasmtime that referenced this issue May 16, 2023
* rename host runtime tests to command tests

* add a test for using wasi in a reactor

* commit cargo.lock

* reactor tests: fix wit deps

* test-programs: reactor-tests can build on stable

note that this fails because it exposes wasi-libc ctors calling import
functions from inside cabi_realloc

* test-programs: show that ctors fix in wit-bindgen fixes bug

* ci: install wasm32 targets for stable as well as nightly

* wit-bindgen: use 0.4.0

* ci: use wit-bindgen 0.4.0

* Co-habitate with wasi-common from wasmtime

* adapter: code motion in cargo feature & artifact names to cli-command, cli-reactor

there will shortly be a third type of reactor (non-cli, idk what to call it)

---------

Co-authored-by: Trevor Elliott <telliott@fastly.com>
dhil pushed a commit to dhil/wasmtime that referenced this issue Mar 28, 2024
…#144)

This PR renames `ContinuationObject` to `VMContRef` and
`ContinuationReference` to `VMContObj`.

This was mostly just a search-replace job, but also involved renaming
lots of variables named things like `contref` or `contobj` (and various
variations thereof), as well as replacing mentions of "continuation
object" in text.

The baseline implementation remains mostly unchanged since it was
already using that nomenclature, only some minor changes at the
boundaries/when interacting with functions defined in both
implementations (e.g.,
`typed_continuations_load_continuation_reference`) were necessary.

This resolves bytecodealliance#104.
avanhatt pushed a commit to wellesley-prog-sys/wasmtime that referenced this issue Oct 9, 2024
Change the `isa_load` state to measure load size in bits instead of
bytes.

Updates avanhatt#49 avanhatt#35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
wasi:api Issues pertaining to the WASI API, not necessarily specific to Wasmtime.
Projects
None yet
Development

No branches or pull requests

3 participants