cranelift

12016 Commits

49 Branches

140 Tags

128 MiB

Tree: 5eec60ab12

Commit Graph

Author	SHA1	Message	Date
Alex Crichton	2897e409db	Remove the implementation of wasi-crypto (#6816 ) * Remove the implementation of wasi-crypto This commit is a follow-up to the discussion on #6732. This removes Wasmtime's implementation of the wasi-crypto proposal from in-tree along with its various support in CI, configuration, etc. See the discussion on #6732 for the full information but at a high level the main reasons for removing the implementation at this time are: * There is not currently an active maintainer of the Wasmtime integration here for wasi-crypto. * There are known issues with the code quality of the implementation such as transmutes of guest-owned memory to `&'static mut [u8]` and known unsafety in dependencies. * The size and breadth of the dependency tree brings maintenance burden and overhead to managing Wasmtime's dependency tree. As mentioned on the issue this commit does not mean that Wasmtime doesn't want to implement the wasi-crypto proposal. Instead the "tier 3" status of wasi-crypto needs to be re-attained to be included back in-tree, which would mean resolving the above issues. Note that this commit is intentionally just after the 13.0.0 branch point which means that this is slated for Wasmtime 14 to be released on September 20. * Remove some cfgs * Remove wasi-crypto CI	1 year ago
Andrew Brown	eaf4e9d3cc	doc: add a page listing supported proposals (#5781 ) * doc: add a page listing supported proposals This adds a table showing Wasmtime's support for various WASI proposals, much like the one available for WebAssembly proposals. This change is related to [#2423], which provides guidelines for implementing WASI proposals but was never merged. [#2423]: https://github.com/bytecodealliance/wasmtime/pull/2423 * review: remove phase-gating sentence	2 years ago

Author

SHA1

Message

Date

Alex Crichton

2897e409db

Remove the implementation of wasi-crypto (#6816 )

* Remove the implementation of wasi-crypto

This commit is a follow-up to the discussion on #6732. This removes
Wasmtime's implementation of the wasi-crypto proposal from in-tree along
with its various support in CI, configuration, etc. See the discussion
on #6732 for the full information but at a high level the main reasons
for removing the implementation at this time are:

* There is not currently an active maintainer of the Wasmtime
  integration here for wasi-crypto.
* There are known issues with the code quality of the implementation
  such as transmutes of guest-owned memory to `&'static mut [u8]` and
  known unsafety in dependencies.
* The size and breadth of the dependency tree brings maintenance burden
  and overhead to managing Wasmtime's dependency tree.

As mentioned on the issue this commit does not mean that Wasmtime
doesn't want to implement the wasi-crypto proposal. Instead the "tier 3"
status of wasi-crypto needs to be re-attained to be included back
in-tree, which would mean resolving the above issues.

Note that this commit is intentionally just after the 13.0.0 branch
point which means that this is slated for Wasmtime 14 to be released on
September 20.

* Remove some cfgs

* Remove wasi-crypto CI

1 year ago

Andrew Brown

eaf4e9d3cc

doc: add a page listing supported proposals (#5781 )

* doc: add a page listing supported proposals

This adds a table showing Wasmtime's support for various WASI proposals,
much like the one available for WebAssembly proposals. This change is
related to [#2423], which provides guidelines for implementing WASI
proposals but was never merged.

[#2423]: https://github.com/bytecodealliance/wasmtime/pull/2423

* review: remove phase-gating sentence

2 years ago

2 Commits (5eec60ab12324ab6c2851319e7d3dd884c377286)