mirror of
https://github.com/fluencelabs/wasmer
synced 2025-06-25 14:41:32 +00:00
20d1023abe
* fix(emscripten) Remove unused imports. This patch removes unused imports reported by `rustc` as warnings. * fix(emscripten) Allow unreachable patterns in `_clock_gettime`. The compiler thinks `CLOCK_MONOTONIC_COARSE` is unreachable, which is not always the case. Add an attribute to allow unreachable patterns to remove the warning. * fix(emscripten) Rename unused variables. This patch renames various unused variables by appending an underscore to them. * fix(emscripten) Declare `table` as immutable. The `table` variable in `EmscriptenGlobals::new` was declared as mutable, but it's never mutated. * fix(emscripten) Remove an unnecessary `unsafe` block. * fix(emscripten) Remove duplicate definition of `SO_NOSIGPIPE`. The `SO_NOSIGPIPE` constant is defined in `syscalls/mod.rs` and `syscalls/unix.rs`. It's never used in the first case. We can safely remove it in this file, and keep it in `unix.rs`. * fix(emscripten) `read_string_from_wasm` is used only on Windows. Mark `read_string_from_wasm` as possible deadcode, since it's used only on Windows. * fix(emscripten) Remove `DYNAMICTOP_PTR_DIFF`, `stacktop`, `stack_max`, `dynamic_base` and `dynamic_ptr`. Four functions and one constant are used together but never used inside or outside this file. They are deadcode. * fix(emscripten) Remove `infinity` and `nan` fields of `EmscriptenGlobalsData`. Those fields are never used. * fix(emscripten) Allow non snake case in `emscripten_target.rs`. Many functions in this file don't follow the snake case style for Rust function names. The reason is that we want the names to match the emscripten symbol names; even if a mapping is done in `lib.rs`, it's easier to get the same names. * fix(emscripten) Rename `STATIC_TOP` to `static_top`. This variable is not a constant.
68 lines
6.2 KiB
Rust
68 lines
6.2 KiB
Rust
use super::process::abort_with_message;
|
|
use wasmer_runtime_core::vm::Ctx;
|
|
|
|
pub fn nullfunc_i(ctx: &mut Ctx, _x: u32) {
|
|
debug!("emscripten::nullfunc_i {}", _x);
|
|
abort_with_message(ctx, "Invalid function pointer called with signature 'i'. Perhaps this is an invalid value (e.g. caused by calling a virtual method on a NULL pointer)? Or calling a function with an incorrect type, which will fail? (it is worth building your source files with -Werror (warnings are errors), as warnings can indicate undefined behavior which can cause this)");
|
|
}
|
|
|
|
pub fn nullfunc_ii(ctx: &mut Ctx, _x: u32) {
|
|
debug!("emscripten::nullfunc_ii {}", _x);
|
|
abort_with_message(ctx, "Invalid function pointer called with signature 'ii'. Perhaps this is an invalid value (e.g. caused by calling a virtual method on a NULL pointer)? Or calling a function with an incorrect type, which will fail? (it is worth building your source files with -Werror (warnings are errors), as warnings can indicate undefined behavior which can cause this)");
|
|
}
|
|
|
|
pub fn nullfunc_iii(ctx: &mut Ctx, _x: u32) {
|
|
debug!("emscripten::nullfunc_iii {}", _x);
|
|
abort_with_message(ctx, "Invalid function pointer called with signature 'iii'. Perhaps this is an invalid value (e.g. caused by calling a virtual method on a NULL pointer)? Or calling a function with an incorrect type, which will fail? (it is worth building your source files with -Werror (warnings are errors), as warnings can indicate undefined behavior which can cause this)");
|
|
}
|
|
|
|
pub fn nullfunc_iiii(ctx: &mut Ctx, _x: u32) {
|
|
debug!("emscripten::nullfunc_iiii {}", _x);
|
|
abort_with_message(ctx, "Invalid function pointer called with signature 'iiii'. Perhaps this is an invalid value (e.g. caused by calling a virtual method on a NULL pointer)? Or calling a function with an incorrect type, which will fail? (it is worth building your source files with -Werror (warnings are errors), as warnings can indicate undefined behavior which can cause this)");
|
|
}
|
|
|
|
pub fn nullfunc_iiiii(ctx: &mut Ctx, _x: u32) {
|
|
debug!("emscripten::nullfunc_iiiii {}", _x);
|
|
abort_with_message(ctx, "Invalid function pointer called with signature 'iiiii'. Perhaps this is an invalid value (e.g. caused by calling a virtual method on a NULL pointer)? Or calling a function with an incorrect type, which will fail? (it is worth building your source files with -Werror (warnings are errors), as warnings can indicate undefined behavior which can cause this)");
|
|
}
|
|
|
|
pub fn nullfunc_iiiiii(ctx: &mut Ctx, _x: u32) {
|
|
debug!("emscripten::nullfunc_iiiiii {}", _x);
|
|
abort_with_message(ctx, "Invalid function pointer called with signature 'iiiiii'. Perhaps this is an invalid value (e.g. caused by calling a virtual method on a NULL pointer)? Or calling a function with an incorrect type, which will fail? (it is worth building your source files with -Werror (warnings are errors), as warnings can indicate undefined behavior which can cause this)");
|
|
}
|
|
|
|
pub fn nullfunc_v(ctx: &mut Ctx, _x: u32) {
|
|
debug!("emscripten::nullfunc_v {}", _x);
|
|
abort_with_message(ctx, "Invalid function pointer called with signature 'v'. Perhaps this is an invalid value (e.g. caused by calling a virtual method on a NULL pointer)? Or calling a function with an incorrect type, which will fail? (it is worth building your source files with -Werror (warnings are errors), as warnings can indicate undefined behavior which can cause this)");
|
|
}
|
|
|
|
pub fn nullfunc_vi(ctx: &mut Ctx, _x: u32) {
|
|
debug!("emscripten::nullfunc_vi {}", _x);
|
|
abort_with_message(ctx, "Invalid function pointer called with signature 'vi'. Perhaps this is an invalid value (e.g. caused by calling a virtual method on a NULL pointer)? Or calling a function with an incorrect type, which will fail? (it is worth building your source files with -Werror (warnings are errors), as warnings can indicate undefined behavior which can cause this)");
|
|
}
|
|
|
|
pub fn nullfunc_vii(ctx: &mut Ctx, _x: u32) {
|
|
debug!("emscripten::nullfunc_vii {}", _x);
|
|
abort_with_message(ctx, "Invalid function pointer called with signature 'vii'. Perhaps this is an invalid value (e.g. caused by calling a virtual method on a NULL pointer)? Or calling a function with an incorrect type, which will fail? (it is worth building your source files with -Werror (warnings are errors), as warnings can indicate undefined behavior which can cause this)");
|
|
}
|
|
|
|
pub fn nullfunc_viii(ctx: &mut Ctx, _x: u32) {
|
|
debug!("emscripten::nullfunc_viii {}", _x);
|
|
abort_with_message(ctx, "Invalid function pointer called with signature 'viii'. Perhaps this is an invalid value (e.g. caused by calling a virtual method on a NULL pointer)? Or calling a function with an incorrect type, which will fail? (it is worth building your source files with -Werror (warnings are errors), as warnings can indicate undefined behavior which can cause this)");
|
|
}
|
|
|
|
pub fn nullfunc_viiii(ctx: &mut Ctx, _x: u32) {
|
|
debug!("emscripten::nullfunc_viiii {}", _x);
|
|
abort_with_message(ctx, "Invalid function pointer called with signature 'viiii'. Perhaps this is an invalid value (e.g. caused by calling a virtual method on a NULL pointer)? Or calling a function with an incorrect type, which will fail? (it is worth building your source files with -Werror (warnings are errors), as warnings can indicate undefined behavior which can cause this)");
|
|
}
|
|
|
|
pub fn nullfunc_viiiii(ctx: &mut Ctx, _x: u32) {
|
|
debug!("emscripten::nullfunc_viiiii");
|
|
abort_with_message(ctx, "Invalid function pointer called with signature 'viiiii'. Perhaps this is an invalid value (e.g. caused by calling a virtual method on a NULL pointer)? Or calling a function with an incorrect type, which will fail? (it is worth building your source files with -Werror (warnings are errors), as warnings can indicate undefined behavior which can cause this)");
|
|
}
|
|
|
|
pub fn nullfunc_viiiiii(ctx: &mut Ctx, _x: u32) {
|
|
debug!("emscripten::nullfunc_viiiiii");
|
|
abort_with_message(ctx, "Invalid function pointer called with signature 'viiiiii'. Perhaps this is an invalid value (e.g. caused by calling a virtual method on a NULL pointer)? Or calling a function with an incorrect type, which will fail? (it is worth building your source files with -Werror (warnings are errors), as warnings can indicate undefined behavior which can cause this)");
|
|
}
|