| /wasmtime-44.0.1/ |
| H A D | CODE_OF_CONDUCT.md | 3 *Note*: this Code of Conduct pertains to individuals' behavior. Please also see the [Organizational…
11 Examples of behavior that contributes to creating a positive environment include:
19 Examples of unacceptable behavior by participants include:
29 …f acceptable behavior and are expected to take appropriate and fair corrective action in response …
39 Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting t…
|
| H A D | ORG_CODE_OF_CONDUCT.md | 3 *Note*: this Code of Conduct pertains to organizations' behavior. Please also see the [Individual C…
123 Instances of organizational behavior in violation of the OCoC may
|
| /wasmtime-44.0.1/docs/ |
| H A D | contributing-fuzzing.md | 47 reproduce the buggy behavior with the test case. These steps should include
53 * **Expected behavior:** A description of the expected, non-buggy behavior, as
54 well as your rationale for *why* that behavior is expected. For example, just
58 below](#divergent-webassembly-behavior-across-runtimes) for examples of known divergent
59 behavior of one module in two runtimes. If applicable, make sure to account
62 * **Actual behavior:** A description of the actual, buggy behavior. This should
74 ### Divergent WebAssembly behavior across runtimes
112 * **WASIp1 API behavior** - the initial specification of WASI, WASIp1 or
|
| H A D | stability-release.md | 50 Each major release of Wasmtime reserves the right to break both behavior and API
54 * Minor breaking changes, either behavior or with APIs, will be documented in
97 correctness issues for on-by-default behavior in supported releases. For example
106 Patch releases are guaranteed to maintain API and behavior
|
| H A D | contributing-reducing-test-cases.md | 43 First, we needed a predicate script to identify the reported buggy behavior. The
119 should exhibit the same behavior as the original.
|
| H A D | security.md | 45 - There is no undefined behavior. Even where the WebAssembly spec permits
46 multiple possible behaviors, it doesn't permit arbitrary behavior.
|
| H A D | contributing-architecture.md | 297 specification's required behavior.
433 is independent from all the others and is a knob for just its behavior. In this
435 additionally has different default behavior across platforms, such as 32-bit and
|
| /wasmtime-44.0.1/cranelift/codegen/src/opts/ |
| H A D | README.md | 90 they can result in surprising multi-matching behavior. Be skeptical of
91 helpers that can inadvertently create this behavior.
99 However, this can also result in surprising behavior. If one has a helper
110 Then this can result in the extremely surprising behavior that `(ireduce
|
| /wasmtime-44.0.1/crates/test-programs/ |
| H A D | README.md | 15 this suite has particular behavior which interacts with the tests themselves.
23 behavior which interacts with the commands and arguments passed to the
58 examining the behavior when the standard output of one instance is piped to
61 to select the behavior of producing output to stdout, or consuming input
|
| /wasmtime-44.0.1/cranelift/docs/ |
| H A D | ir.md | 332 Traps stop the program because something went wrong. The exact behavior depends
427 If the memory at the given address is not [addressable], the behavior of
447 When the `accessible` flag is set, the behavior is undefined if the memory
582 have special behavior for signaling NaN operands. The exponent and trailing
608 These instructions succeed, trap, or have undefined behavior, under the same
709 Memory in which loads and stores have defined behavior. They either
805 Terminates execution of the current thread. The specific behavior after
806 a trap depends on the underlying OS. For example, a common behavior is
|
| /wasmtime-44.0.1/tests/misc_testsuite/component-model/async/ |
| H A D | backpressure-deadlock.wast | 13 ;; cancelling tasks, that behavior may change, in which case this test will need
|
| H A D | error-context.wast | 38 ;; Test edge-case behavior of `error-context.debug-message`.
|
| /wasmtime-44.0.1/tests/misc_testsuite/custom-page-sizes/ |
| H A D | custom-page-sizes.wast | 13 ;; Check the behavior of memories with page size 1.
|
| /wasmtime-44.0.1/crates/explorer/src/ |
| H A D | index.js | 145 behavior: "smooth", property
|
| /wasmtime-44.0.1/crates/debugger/wit/deps/ |
| H A D | io.wit | 147 /// be read. Except for blocking, behavior is identical to `read`.
157 /// can be skipped. Except for blocking behavior, identical to `skip`.
300 /// The behavior of splice is equivalent to:
|
| /wasmtime-44.0.1/crates/wasi/src/p2/wit/deps/ |
| H A D | io.wit | 147 /// be read. Except for blocking, behavior is identical to `read`.
157 /// can be skipped. Except for blocking behavior, identical to `skip`.
300 /// The behavior of splice is equivalent to:
|
| /wasmtime-44.0.1/crates/wasi-http/wit/deps/ |
| H A D | io.wit | 147 /// be read. Except for blocking, behavior is identical to `read`.
157 /// can be skipped. Except for blocking behavior, identical to `skip`.
300 /// The behavior of splice is equivalent to:
|
| /wasmtime-44.0.1/crates/wasi-tls/wit/deps/ |
| H A D | io.wit | 147 /// be read. Except for blocking, behavior is identical to `read`.
157 /// can be skipped. Except for blocking behavior, identical to `skip`.
300 /// The behavior of splice is equivalent to:
|
| /wasmtime-44.0.1/crates/wasi-io/wit/deps/ |
| H A D | io.wit | 147 /// be read. Except for blocking, behavior is identical to `read`.
157 /// can be skipped. Except for blocking behavior, identical to `skip`.
300 /// The behavior of splice is equivalent to:
|
| /wasmtime-44.0.1/crates/wasi/src/p3/wit/deps/ |
| H A D | sockets.wit | 209 /// behavior and SO_REUSEADDR performs something different.
291 /// > socket as an error code from accept(). This behavior differs from
311 /// exhibit this behavior out of the box. On platforms that require it,
312 /// the WASI implementation can emulate this behavior by performing
437 /// The keepalive behavior can be adjusted using:
662 /// this behavior natively. On such platforms, the WASI implementation
|
| H A D | cli.wit | 79 /// Multiple streams may be active at the same time. The behavior of concurrent
|
| /wasmtime-44.0.1/crates/wasi-http/src/p3/wit/deps/ |
| H A D | sockets.wit | 209 /// behavior and SO_REUSEADDR performs something different.
291 /// > socket as an error code from accept(). This behavior differs from
311 /// exhibit this behavior out of the box. On platforms that require it,
312 /// the WASI implementation can emulate this behavior by performing
437 /// The keepalive behavior can be adjusted using:
662 /// this behavior natively. On such platforms, the WASI implementation
|
| H A D | cli.wit | 79 /// Multiple streams may be active at the same time. The behavior of concurrent
|
| /wasmtime-44.0.1/cranelift/isle/docs/ |
| H A D | language-reference.md | 383 factor common behavior out of multiple rules, or aids in conceptual
785 More precisely, a term, like `A`, can have three kinds of behavior
798 Constructor behavior on a term allows it to be invoked in the
807 Extractor behavior on a term allows it to be used in a pattern in the
842 attempts (via whatever programmable matching behavior) to use `A` to
847 extractors. Most of the interesting programmable behavior occurs in
1205 should be marked `partial`). If fallible behavior is needed when
1206 invoking external Rust code, that behavior should occur in an extractor
1212 An *external extractor* is an implementation of matching behavior in
|
| /wasmtime-44.0.1/crates/wasmtime/src/runtime/ |
| H A D | store.rs | 2817 let mut behavior = self.epoch_deadline_behavior.take(); in new_epoch_updated_deadline() localVariable
2818 let update = match &mut behavior { in new_epoch_updated_deadline()
2824 self.epoch_deadline_behavior = behavior; in new_epoch_updated_deadline()
|