|
Revision tags: dev, v36.0.9, v44.0.1, v43.0.2, v36.0.8, v24.0.8, v44.0.0, v43.0.1, v42.0.2, v36.0.7, v24.0.7, v43.0.0, v42.0.1, v41.0.4, v42.0.0, v40.0.4, v36.0.6, v24.0.6, v41.0.3, v41.0.2, v41.0.1, v36.0.5, v40.0.3, v41.0.0, v36.0.4, v39.0.2, v40.0.2, v40.0.1, v40.0.0, v39.0.1, v39.0.0, v38.0.4, v37.0.3, v36.0.3, v24.0.5, v38.0.3, v38.0.2, v38.0.1, v37.0.2, v37.0.1, v37.0.0, v36.0.2, v36.0.1, v36.0.0, v35.0.0, v24.0.4, v33.0.2, v34.0.2, v34.0.1, v33.0.1, v24.0.3, v32.0.1, v34.0.0 |
|
| #
5603ee7b |
| 03-Jun-2025 |
Alex Crichton <[email protected]> |
Change component/instance maps to `PrimaryMap` (#10916)
* Change component/instance maps to `PrimaryMap`
This switches to using typed keys for these maps to be more idiomatic with the rest of Wasmt
Change component/instance maps to `PrimaryMap` (#10916)
* Change component/instance maps to `PrimaryMap`
This switches to using typed keys for these maps to be more idiomatic with the rest of Wasmtime and this has the additional benefit of compressing indices to 32-bits instead of the previous pointer-sized-bits.
* Fix an unused import
show more ...
|
| #
8fb9d189 |
| 03-Jun-2025 |
Alex Crichton <[email protected]> |
Remove `Stored` usage from `wasmtime::component::Instance` (#10913)
* Remove mutability required on a number of component methods
Powered by previous refactorings it's possible to just take `&Store
Remove `Stored` usage from `wasmtime::component::Instance` (#10913)
* Remove mutability required on a number of component methods
Powered by previous refactorings it's possible to just take `&StoreOpaque` in these locations.
* Move core instance map into `ComponentInstance`
This commit moves the mapping from a `RuntimeInstanceIndex` to a `wasmtime::Instance` from `wasmtime::component::InstanceData` into the internal `ComponentInstance` structure. This is done in preparation to remove `InstanceData` eventually.
* Move `Component` to live in `ComponentInstance`
Previously this lived in `InstanceData` but that's just a historical artifact of the old `wasmtime` and `wasmtime-runtime` split. Nowadays it's possible to store `Component` directly to further move information out of `InstanceData`.
* Move `InstanceData::imports` to `ComponentInstance`
More preparation for the removal of `InstanceData` entirely.
* Move lookup functions from `InstanceData` to `ComponentInstance`
More prep for the removal of `InstanceData`.
* Reduce some more reliance on `InstanceState`
Just removing it from some type signatures to make future removal easier.
* Remove an unused result from a helper function
No caller needs it, so go ahead and remove it.
* Make `ComponentInstance::imports` private
This moves some methods around and documents preexisting `unsafe` contracts to get this field private and prevent external access to it.
* Remove `InstanceData` from `Instantiator`.
Use `OwnedComponentInstance` instead.
* Remove `InstanceData`, refactor `Instance`
This commit refactors the representation of `component::Instance` to be purely index-based to data already within a store. This makes creation of an `Instance` free compared to before where auxiliary data needed to be created. Note that this doesn't actually change storage within a `Store<T>` as instances are still there, it's just that now the storage lives in a non-`Stored`-related location.
show more ...
|
| #
b2c64de1 |
| 23-May-2025 |
MangoPeachGrape <[email protected]> |
c-api: component-model: Values and function calling (#10697)
* c-api: component-model: Primitive values
* c-api: component-model: Function calling
* A test
* Take args as mut to avoid copying
*
c-api: component-model: Values and function calling (#10697)
* c-api: component-model: Primitive values
* c-api: component-model: Function calling
* A test
* Take args as mut to avoid copying
* String and char
* Rethink value ownership semantics, add list values
* Record values
* Make take Rust values as refs in `::from()` functions
Later we can provide implementations that take it as a value to avoid copying
* Define host functions
* `wasmtime_component_valrecord_new()`
* Use `u32` instead of `char` as its not ffi safe
* Test records and strings in c-api -> vm -> host func -> vm -> c-api
* `wasmtime_component_vallist_new()`
* Test lists
* Fix formatting
* Use existing `declare_vecs` construct
* Add rest of helper functions
* Add documentation
* Fix multiline comments
* Third time's the charm
* Fourth time's the charm prtest:full
* Doxygen file headers
* Fix other missing documentation
* Small fix to docs
show more ...
|
|
Revision tags: v33.0.0 |
|
| #
ce3c1a72 |
| 28-Apr-2025 |
MangoPeachGrape <[email protected]> |
c-api: component-model: Lookup function from an instance (#10675)
* c-api: component-model: Lookup function from an instance
* c-api: component-model: Take strings as `wasm_name_t`
* Use export in
c-api: component-model: Lookup function from an instance (#10675)
* c-api: component-model: Lookup function from an instance
* c-api: component-model: Take strings as `wasm_name_t`
* Use export indices
* Shared `CHECK_ERR` macro
* Pass names as a pointer and a size, return nullable pointers
* Use `std::str::from_utf8()` instead of `str::from_utf8()`
* Remove doc link?
show more ...
|
|
Revision tags: v32.0.0 |
|
| #
930d3543 |
| 18-Apr-2025 |
MangoPeachGrape <[email protected]> |
c-api: Create and instantiate a component model linker (#10598)
* c-api: Create and instantiate a component model linker
Co-authored-by: Tyler Rockwood <[email protected]> Co-authored-by: Jean-
c-api: Create and instantiate a component model linker (#10598)
* c-api: Create and instantiate a component model linker
Co-authored-by: Tyler Rockwood <[email protected]> Co-authored-by: Jean-Jacques Lafay <[email protected]>
* c-api: Accept `wat` in `wasmtime_component_new()`
* Add a test
* c-api: Include `wasmtime/conf.h` in `component/component.h`
* Add `wasmtime/conf.h` include to `instance.h` and `linker.h`
* Make wasmtime_component_instance_t non-opaque
* Defer `wasmtime_component_linker_instance()`
---------
Co-authored-by: Tyler Rockwood <[email protected]> Co-authored-by: Jean-Jacques Lafay <[email protected]>
show more ...
|