Crates.io | hc-wasmer-compiler |
lib.rs | hc-wasmer-compiler |
version | 4.3.6-hc.1 |
source | src |
created_at | 2024-08-27 21:37:05.82685 |
updated_at | 2024-08-28 17:30:01.747964 |
description | Base compiler abstraction for Wasmer WebAssembly runtime |
homepage | https://wasmer.io/ |
repository | https://github.com/wasmerio/wasmer |
max_upload_size | |
id | 1353854 |
size | 226,646 |
wasmer-compiler
This crate is the base for Compiler implementations.
It performs the translation from a Wasm module into a basic
ModuleInfo
, but leaves the Wasm function bytecode translation to the
compiler implementor.
Here are some of the Compilers provided by Wasmer:
To create a compiler, one needs to implement two traits:
CompilerConfig
, that configures and creates a new compiler,Compiler
, the compiler itself that will compile a module./// The compiler configuration options.
pub trait CompilerConfig {
/// Gets the custom compiler config
fn compiler(&self) -> Box<dyn Compiler>;
}
/// An implementation of a compiler from parsed WebAssembly module to compiled native code.
pub trait Compiler {
/// Compiles a parsed module.
///
/// It returns the [`Compilation`] or a [`CompileError`].
fn compile_module<'data, 'module>(
&self,
target: &Target,
compile_info: &'module CompileModuleInfo,
module_translation: &ModuleTranslationState,
// The list of function bodies
function_body_inputs: PrimaryMap<LocalFunctionIndex, FunctionBodyData<'data>>,
) -> Result<Compilation, CompileError>;
}
This project borrowed some of the code strucutre from the
cranelift-wasm
crate, however it's been adapted to not depend on
any specific IR and be abstract of any compiler.
Please check Wasmer ATTRIBUTIONS
to further see licenses and other
attributions of the project.