I più scaricati: Dati aggiornati al 12 novembre 2026

Categorie

Internet1409
Comunicazione327
Audio e video931
Grafica e design563
Ufficio e produttività1167
Strumenti di sviluppo3263
Strumenti di IA600
Sicurezza e privacy406
Strumenti di sistema3174
Giochi543
Istruzione e scienza240
Rete e IT292

Scarica Wasmtime 14.0.0 per Windows

A fast and secure runtime for WebAssembly

Questa è una versione precedente. La versione attuale è la 50.0.1. Wasmtime 50.0.1 · Data di rilascio:

File di installazione 14.0.0

ArchitetturaTipoAmbitoDimensioneScaricaSHA256
64 bit MSI Tutti gli utenti — github.com VirusTotal

Link e hash SHA256 provengono dal manifest della community di Gestione pacchetti Windows. Prima di eseguire il file scaricato conviene confrontarne l’hash.

Note di rilascio

One of the larger changes in this release is a redesign of Wasmtime's CLI arguments and where arguments are passed. This means that previous invocations of the wasmtime CLI executable will need to be updated. No functionality was removed but most of it is behind new flags. One major change is that Wasmtime CLI flags are now grouped behind short options like -O. For example

wasmtime run --opt-level 2 foo.wasm

is now:

wasmtime run -O opt-level=2 foo.wasm

Additionally options prefixed with --enable-* or --disable-* now consistently are considered boolean setters. For example:

wasmtime run --disable-cache foo.wasm

is now:

wasmtime run -C cache=n foo.wasm

Options can be explored with wasmtime -C help for example, and wasmtime -h will show all option groups that can be expanded.

Another major change in the CLI is that any CLI argument which positionally comes after the wasm file specified will be passed as an argument to the guest module. For example this invocations

wasmtime run foo.wasm --epoch-interruption

was previously accepted as enabling epoch interruption for the foo.wasm file. This is now interpreted as if it were ./foo.wasm --epoch-interruption, however, passing the flag to the wasm file itself. Flags to Wasmtime must now come after Wasmtime's subcommand (in this case run) and before the wasm file that's being run, for example:

wasmtime run -W epoch-interruption foo.wasm

More information about this change can be found on #6925 and #6946.

Added
- Added the wasmtime::FrameInfo::module method, which returns the wasmtime::Module associated with the stack frame.
- The wasmtime::component::Linker type now implements Clone. #7032
- Wasmtime's TypedFunc API now supports the v128 WebAssembly type on x86_64 and aarch64. #7010
- Support for resources exported from a WebAssembly guest has been added to the component bindgen! macro. #7050
- The C API now supports learning about a module's image_range. #7064
- Passing values between components is now possible with a more complete implementation of type-checking of values. #7065
- Types representing resources can now be customized with bindgen!. #7069
- Wasm-defined globals and memories are now included in core dumps, and the wasmtime::WasmCoreDump type is now serializable. #6935 #7078
- Initial experimental support for Intel MPK has been added to support running more instances concurrently. #7072
- The implementation of wasi:http now supports inbound requests in addition to outbound requests. A new wasmtime serve command is an example way of handling http requests with wasm files. #7091
- The C API now supports Wasmtime's "host memory creation" API to customize the allocation of linear memories. #7115
- The C API now supports asynchronous invocation of WebAssembly programs. #7106
- The C API now supports Wasmtime's InstancePre<T> type. #7140
- The wasi:sockets/ip-name-lookup interface is now implemented by Wasmtime. #7109

Changed
- Wasmtime's CLI has been significantly overhauled. See the note above. #6925 #6946
- The wasmtime::FrameInfo::module_name has been removed, however you can now get identical results by chaining wasmtime::FrameInfo::module and wasmtime::Module::name: my_frame.module().name().
- WASI interfaces have seen significant work since the previous release. Streams for example have a new backpressure and flushing design. Additionally WIT resources are now used ubiquitously throughout the specification and implementation. #6877 #7029 #7090
- The implementation of wasi:http now uses {input,output}-stream from the wasi:io/streams interface. #7056
- Lifting and lowering of the list<u8> component values has been significantly optimized. #6971
- The wasmtime-c-api crate is now additionally built as an rlib as well as the previous cdylib/staticlib combo. #6765

Fixed
- Support referencing stack slots in the DWARF debug info. #6960
- Printing unicode to stdio on Windows has been fixed. #6825
- Building for x86_64-linux-android has been fixed. #7055
- Fixed stdout/stderr becoming nonblocking by accident with WASI preview2 on macOS. #7058
- Fixed some character boundary-related panics in the preview2 implementation of preview1. #7011
- Fixed an issue of guests sleeping for an incorrect amount of time with preview2. #6993
- Cranelift will now return an error when running out of temporaries in a very large function instead of panicking. #7114

https://github.com/bytecodealliance/wasmtime/blob/main/RELEASES.md#1400

Il più popolare in Linguaggi e SDK

Vedi tutti
  1. LLVMLinguaggi e SDK · LLVM
  2. DenoLinguaggi e SDK · Deno Land Inc.
  3. CMakeLinguaggi e SDK · Kitware
  4. YarnLinguaggi e SDK · Yarn Contributors
  5. pnpmLinguaggi e SDK · pnpm
  6. CcacheLinguaggi e SDK · Joel Rosdahl
  7. sbtLinguaggi e SDK · Lightbend, Inc.
  8. BOINCLinguaggi e SDK · Space Sciences Laboratory, U.C. Berkeley
  9. Dart SDKLinguaggi e SDK · Google

Tag

Condividi