Add wasi:http support to the C API (#12950)

Reexport pulley/all-arch through the C API (#11504)

This commit adds a few more features from the Wasmtime crate to the C
API for pulley and the all-arch option for Cranelift to support
compiling fo

Reexport pulley/all-arch through the C API (#11504)

This commit adds a few more features from the Wasmtime crate to the C
API for pulley and the all-arch option for Cranelift to support
compiling for multiple architectures.

show more ...

c-api: Compile a component (#10566)

* c-api: Compile a component

Co-authored-by: Tyler Rockwood <[email protected]>
Co-authored-by: Jean-Jacques Lafay <[email protected]>

* Add docu

c-api: Compile a component (#10566)

* c-api: Compile a component

Co-authored-by: Tyler Rockwood <[email protected]>
Co-authored-by: Jean-Jacques Lafay <[email protected]>

* Add documentation to config

---------

Co-authored-by: Tyler Rockwood <[email protected]>
Co-authored-by: Jean-Jacques Lafay <[email protected]>

show more ...

Allow setting pooling allocation in the C API (#10484)

* Allow setting pooling allocation in the C API

* Formatting

* Switch to object-style API

* Delete function

* Add wasmtime_ prefix

* More

Allow setting pooling allocation in the C API (#10484)

* Allow setting pooling allocation in the C API

* Formatting

* Switch to object-style API

* Delete function

* Add wasmtime_ prefix

* More documentation and minor fixes

* Update doxygen config to exclude the WASMTIME_POOLING_ALLOCATION_CONFIG_PROP macro.

show more ...

c-api: Enable debugger DWARF export for guest code (#9915)

* c-api: Enable debugger DWARF export for guest code

In order to allow source level debugging of hosted webassembly code in
C-based embedd

c-api: Enable debugger DWARF export for guest code (#9915)

* c-api: Enable debugger DWARF export for guest code

In order to allow source level debugging of hosted webassembly code in
C-based embeddings, we must enable the debug-builtins cargo feature when
building the C api.

* c-api test: assert that the debug info is created

Previously we were testing and confirming only that the options can be
set using the API, not that they actually have any effect.

In order to (simply) confirm that enabling debug information actually
created some debug information, we can somewhat hackily inspect the
generated GDB JIT descriptor to see that it's populated.

show more ...

Add the "null" garbage collector (#9484)

* Add the "null" garbage collector

The null collector does not actually collect any garbage, it simply
bump-allocates until the heap is exhausted, at which

Add the "null" garbage collector (#9484)

* Add the "null" garbage collector

The null collector does not actually collect any garbage, it simply
bump-allocates until the heap is exhausted, at which point further allocation
attempts will fail. It does not require any GC barriers.

Users can configure which collector to use via the `wasmtime::Config::collector`
method or the `-C collector=drc|null` CLI flag. The `wasmtime::Collector` enumeration,
similar to the `wasmtime::Strategy` enumeration but for choosing a collector
rather than a compiler, additionally has a table summarizing the properties and
characteristics of our current set of collector implementations.

Finally, we also run `.wast` tests that exercise GC types under both the DRC and
null collectors. I tried to avoid running tests that are not related to GC under
both configurations just to avoid a combinatorial blow up.

* cargo fmt

* fix +gc -gc-null -gc-drc build

* Fix some warnings in various cargo feature combo builds

* Fix some more warnings in certain build configs

* Fix unit tests for null GC

* Fill in some placeholder comments that I forgot to write

* Fix issues where we ask for a GC store when we don't actually need one

Which was causing test failures, since we no longer return a GC store with a
dummy heap.

* Add fuzzing config support for different collectors

* address review feedback

* fix cmake tests

* Fix test compilation after rebase

* Fix GC tests under MIRI

show more ...

Use cmake to build wasmtime-c-api (#9031)

* Use cmake to build wasmtime-c-api

* Properly expose features when building via cmake

* Install all headers to same directory

* Add vets

* attempt to f

Use cmake to build wasmtime-c-api (#9031)

* Use cmake to build wasmtime-c-api

* Properly expose features when building via cmake

* Install all headers to same directory

* Add vets

* attempt to fix ci

* Run all tests on CI

prtest:full

* Set CARGO_BUILD_TARGET; add CMakeLists to package

* Update comment on github action

* Attempt to fix android build

* Fix source dir modifications of c-api build

* Re-add BINARY_DIR option

* Fix build

* Move header installation to a cmake script

Try to avoid dealing with cmake configuration/platforms/etc.

* Tweak build of headers

* Install headers in build dir for examples

* Add cmake files to dist, fix header install dir

---------

Co-authored-by: Alex Crichton <[email protected]>

show more ...