mii/wasmer
1
0
Fork 0
mirror of https://github.com/mii443/wasmer.git synced 2025-12-03 03:08:22 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix spelling WASM -> Wasm

Browse Source
This commit is contained in:
Simon Warta
2021-01-03 21:59:11 +01:00
parent db41a5dfe8
commit 82e9c0c18f
9 changed files with 15 additions and 15 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/migration_to_1.0.0.md
View File

@@ -20,7 +20,7 @@ to make migrating to the new API as simple as possible.
## Rationale for changes in 1.0.0
Wasmer 0.x was great but as the WASM community and standards evolve we felt the need to make Wasmer also follow these
Wasmer 0.x was great but as the Wasm community and standards evolve we felt the need to make Wasmer also follow these
changes.
Wasmer 1.x is what we think a necessary rewrite of a big part of the project to make it more future-proof.
@@ -70,9 +70,9 @@ The figure above shows the core Wasmer crates and their dependencies with transi
Wasmer 1.0.0 has two core architectural abstractions: engines and compilers.
An engine is a system that processes WASM with a compiler and prepares it to be executed.
An engine is a system that processes Wasm with a compiler and prepares it to be executed.
A compiler is a system that translates WASM into a format that can be understood
A compiler is a system that translates Wasm into a format that can be understood
more directly by a real computer: machine code.
For example, in the [examples] you'll see that we are using the JIT engine and the Cranelift compiler. The JIT engine

6
examples/early_exit.rs
View File

@@ -1,9 +1,9 @@
//! There are cases where you may want to interrupt this synchronous execution of the WASM module
//! There are cases where you may want to interrupt this synchronous execution of the Wasm module
//! while the it is calling a host function. This can be useful for saving resources, and not
//! returning back to the guest WASM for execution, when you already know the WASM execution will
//! returning back to the guest Wasm for execution, when you already know the Wasm execution will
//! fail, or no longer be needed.
//!
//! In this example, we will run a WASM module that calls the imported host function
//! In this example, we will run a Wasm module that calls the imported host function
//! interrupt_execution. This host function will immediately stop executing the WebAssembly module.
//!
//! You can run the example directly by executing in Wasmer root:

2
examples/imports_exports.rs
View File

@@ -93,7 +93,7 @@ fn main() -> Result<(), Box<dyn std::error::Error>> {
// Here we go.
//
// The WASM module exports some entities:
// The Wasm module exports some entities:
// * A function: `guest_function`
// * A global: `guest_global`
// * A memory: `guest_memory`

2
examples/imports_function_env.rs
View File

@@ -2,7 +2,7 @@
//! globals and tables.
//!
//! In this example, we'll create a system for getting and adjusting a counter value. However, host
//! functions are not limited to storing data outside of WASM, they're normal host functions and
//! functions are not limited to storing data outside of Wasm, they're normal host functions and
//! can do anything that the host can do.
//!
//! 1. There will be a `get_counter` function that will return an i32 of

4
lib/c-api/src/deprecated/value.rs
View File

@@ -90,7 +90,7 @@ impl From<wasmer_value_t> for Val {
tag: wasmer_value_tag::WASM_F64,
value: wasmer_value { F64 },
} => Val::F64(F64),
_ => unreachable!("unknown WASM type"),
_ => unreachable!("unknown Wasm type"),
}
}
}
@@ -145,7 +145,7 @@ impl From<wasmer_value_tag> for ValType {
wasmer_value_tag::WASM_I64 => ValType::I64,
wasmer_value_tag::WASM_F32 => ValType::F32,
wasmer_value_tag::WASM_F64 => ValType::F64,
_ => unreachable!("unknown WASM type"),
_ => unreachable!("unknown Wasm type"),
}
}
}

4
lib/compiler-cranelift/src/translator/code_translator.rs
View File

@@ -1432,8 +1432,8 @@ pub fn translate_operator<FE: FuncEnvironment + ?Sized>(
let shuffled = builder.ins().shuffle(a, b, mask);
state.push1(shuffled)
// At this point the original types of a and b are lost; users of this value (i.e. this
// WASM-to-CLIF translator) may need to raw_bitcast for type-correctness. This is due
// to WASM using the less specific v128 type for certain operations and more specific
// Wasm-to-CLIF translator) may need to raw_bitcast for type-correctness. This is due
// to Wasm using the less specific v128 type for certain operations and more specific
// types (e.g. i8x16) for others.
}
Operator::I8x16Swizzle => {

2
tests/wast/spec/memory.wast
View File

@@ -91,7 +91,7 @@
(module
(memory 1)
(data (i32.const 0) "ABC\a7D") (data (i32.const 20) "WASM")
(data (i32.const 0) "ABC\a7D") (data (i32.const 20) "Wasm")
;; Data section
(func (export "data") (result i32)

2
tests/wast/spec/proposals/simd/simd_splat.wast
View File

@@ -342,7 +342,7 @@
(assert_return (invoke "as-i32x4_trunc_s_f32x4_sat-operand" (f32.const 1.1)) (v128.const i32x4 1 1 1 1))
;; As the argument of control constructs and WASM instructions
;; As the argument of control constructs and Wasm instructions
(module
(global $g (mut v128) (v128.const f32x4 0.0 0.0 0.0 0.0))

2
tests/wast/spec/proposals/threads/memory.wast
View File

@@ -95,7 +95,7 @@
(module
(memory 1)
(data (i32.const 0) "ABC\a7D") (data (i32.const 20) "WASM")
(data (i32.const 0) "ABC\a7D") (data (i32.const 20) "Wasm")
;; Data section
(func (export "data") (result i32)