Update GC proposal status in docs (#12918)

After https://github.com/bytecodealliance/wasmtime/pull/12917, we now have
support for the GC proposal in the C and C++ APIs.

Exceptions: add exception-specific (command-sequence) fuzzer. (#12923)

* Exceptions: add exception-specific (command-sequence) fuzzer.

This fuzzer uses a description of a set of "scenarios", arbitr

Exceptions: add exception-specific (command-sequence) fuzzer. (#12923)

* Exceptions: add exception-specific (command-sequence) fuzzer.

This fuzzer uses a description of a set of "scenarios", arbitrarily
generated, to produce a specific kind of module that tests throw/catch
behavior. The module contains a chain of functions that invoke each
other; one will throw, and the rest may have catch clauses that do or
do not catch.

* Review feedback.

show more ...

aarch64: Disable csdb emission by default (#12932)

* aarch64: Disable csdb emission by default

This has a massive performance penalty on macOS, for example, and peer
compilers are not emitting this

aarch64: Disable csdb emission by default (#12932)

* aarch64: Disable csdb emission by default

This has a massive performance penalty on macOS, for example, and peer
compilers are not emitting this as part of on-by-default mitigations.
This commit preserves the option to emit it with an aarch64-specific
`use_csdb` flag, but the default is now `false` meaning that this is not
emitted by default.

Closes #12789

* Fix tests

* Fix tests & review comments

* Use ISLE rule introduced

show more ...

Update exception-handling status in Wasmtime docs: now has C API. (#12919)

After #12861 lands, we have full C/C++ API support for creating,
inspecting, throwing and catching exceptions.

Allow using `demangle` feature in `no_std` builds. (#12740)

While there, add `async`, `debug`, `debug-builtins` and `anyhow` to
the list of features supporting `#![no_std]`, and update the CI job
to

Allow using `demangle` feature in `no_std` builds. (#12740)

While there, add `async`, `debug`, `debug-builtins` and `anyhow` to
the list of features supporting `#![no_std]`, and update the CI job
to include those features.

Signed-off-by: Piotr Sikora <[email protected]>

show more ...

Document the effect of CI outages on releases (#12521)

* Document the effect of CI outages on releases

Clearly specify in our documentation that we are entirely subject to the
shims of Azure and Gi

Document the effect of CI outages on releases (#12521)

* Document the effect of CI outages on releases

Clearly specify in our documentation that we are entirely subject to the
shims of Azure and GitHub Actions. If they're down we just simply can't
do a release and there's nothing we can do about it. Document this both
for ourselves and for external users to understand our own limitations.
An offer is made as well in case a company is willing to donate
resources (e.g. money or engineering) to improve the situation as well.

* Update docs/stability-release.md

Co-authored-by: Nick Fitzgerald <[email protected]>

---------

Co-authored-by: Nick Fitzgerald <[email protected]>

show more ...