| /wasmtime-44.0.1/crates/wasi-common/src/ |
| H A D | clocks.rs | 34 pub system: Option<Box<dyn WasiSystemClock>>, field 41 system: None, in new() 47 self.system = Some(Box::new(clock)); in with_system() 56 pub fn system(&self) -> Result<&dyn WasiSystemClock, Error> { in system() method 57 self.system in system()
|
| /wasmtime-44.0.1/docs/ |
| H A D | cli-cache.md | 26 Please refer to the [cache system] section to learn how it works. 128 If the time has been changed in the system (i.e. two years backwards), 129 the [cache system] should still work properly. 136 The cache system tries to keep these files as long as possible. 152 To learn more, please refer to the [cache system] section. 165 To learn more, please refer to the [cache system] section. 183 To learn more, please refer to the [cache system] section. 199 To learn more, please refer to the [cache system] section. 205 [cache system]: #how-does-the-cache-work 217 There are two main components - the *cache system* and the *cache worker*. [all …]
|
| H A D | cli-install.md | 65 If you have [Rust and Cargo](https://www.rust-lang.org/tools/install) available in your system, you… 77 …to automatically find and install the correct `wasmtime` binary for your system, matching a candid…
|
| H A D | security-what-is-considered-a-security-vulnerability.md | 52 | <ul>File system access outside of the WASI file system's mapped directories | - | Yes |
|
| H A D | cli-logging.md | 8 To enable logging of WASI system calls, similar to the `strace` command on Linux,
|
| H A D | examples-profiling.md | 11 operating system. Because Wasmtime is a JIT, that also requires hooks from
|
| H A D | contributing-building.md | 28 that your system has a `libclang` installed. Therefore, if you want to hack on
|
| H A D | examples-profiling-vtune.md | 47 Note that VTune is capable of profiling a single process or all system 146 - Enable "Hardware Event-Based Sampling," which may require some system
|
| H A D | introduction.md | 13 secure and portable way to access several operating-system-like features such as
|
| /wasmtime-44.0.1/cranelift/jit/src/memory/ |
| H A D | mod.rs | 5 mod system; module 8 pub use system::SystemMemoryProvider;
|
| /wasmtime-44.0.1/crates/wasi-common/ |
| H A D | Cargo.toml | 35 system-interface = { workspace = true, features = ["cap_std_impls"], optional = true } 86 "dep:system-interface",
|
| /wasmtime-44.0.1/.github/ISSUE_TEMPLATE/ |
| H A D | wasmtime-bug-report.md | 36 Operating system: TODO
|
| H A D | clif-bug-report.md | 37 Operating system: TODO
|
| /wasmtime-44.0.1/examples/min-platform/ |
| H A D | README.md | 5 WebAssembly outside of Linux on a smaller system with a custom operating system
|
| /wasmtime-44.0.1/crates/wasi/src/p3/wit/deps/ |
| H A D | clocks.wit | 66 interface system-clock { 109 use system-clock.{instant}; 158 import system-clock;
|
| H A D | filesystem.wit | 26 /// across all platforms. Notably, depending on the underlying operating system 27 /// and file system: 41 use wasi:clocks/system[email protected].{instant}; 174 /// Set the timestamp to the current time of the system clock associated 260 /// Read-only file system, similar to `EROFS` in POSIX. 570 import wasi:clocks/system[email protected];
|
| /wasmtime-44.0.1/crates/wasi-http/src/p3/wit/deps/ |
| H A D | clocks.wit | 66 interface system-clock { 109 use system-clock.{instant}; 158 import system-clock;
|
| H A D | filesystem.wit | 26 /// across all platforms. Notably, depending on the underlying operating system 27 /// and file system: 41 use wasi:clocks/system[email protected].{instant}; 174 /// Set the timestamp to the current time of the system clock associated 260 /// Read-only file system, similar to `EROFS` in POSIX. 570 import wasi:clocks/system[email protected];
|
| /wasmtime-44.0.1/cranelift/isle/docs/ |
| H A D | language-reference.md | 73 a general-purpose term-rewriting base. Covers the type system (typed 98 section](#core-isle-a-term-rewriting-system).* 102 or TRS, is a system that works by representing data as *terms* and 107 is the system's output. 109 Term-rewriting systems are a general kind of computing system, at the 138 latter (the "strategy") at will without breaking the system's 229 The heart of a term-rewriting system is in the set of *rules* that 426 application of a term-rewriting system should not depend for 457 term-rewriting system, with a design that very closely follows the 462 term-rewriting system, especially one designed for instruction [all …]
|
| /wasmtime-44.0.1/crates/c-api/ |
| H A D | README.md | 34 depends on your operating system. 37 extension depends on your operating system.
|
| /wasmtime-44.0.1/crates/wasi-preview1-component-adapter/provider/ |
| H A D | README.md | 62 To standardize underlying system interoperability (ex. reading files, system time) in code compiled…
|
| /wasmtime-44.0.1/crates/wasi-nn/examples/classification-example-pytorch/ |
| H A D | README.md | 6 your system.
|
| /wasmtime-44.0.1/crates/wasi/ |
| H A D | Cargo.toml | 38 system-interface = { workspace = true}
|
| /wasmtime-44.0.1/cranelift/docs/ |
| H A D | compare-llvm.md | 104 This biases the overall system towards fast compilation when mid-level 140 [Cranelift's type system](ir.md#value-types) is mostly a subset of LLVM's type 141 system. It is less abstract and closer to the types that common ISA registers
|
| /wasmtime-44.0.1/crates/wiggle/tests/ |
| H A D | typenames.witx | 122 ;;; Too many files open in system. 178 ;;; Read-only file system. 325 ;;; File serial number that is unique within its file system. 415 ;;; Identifier for a device containing a file system. Can be used in combination 687 ;;; Bad system call.
|