09c6c5db44
* move trap site definitions into cranelift-module `cranelift-faerie` and `cranelift-object` already have identical definitions of structures to represent trap sites. We might as well merge them ahead of work to define functions via a raw slice of bytes with associated traps, which will need some kind of common structure for representing traps anyway. * cranelift-module: add `define_function_bytes` interface This interface is useful when the client needs to precisely specify the ordering of bytes in a particular function. * add comment about saving files for `perf`
23 lines
658 B
Rust
23 lines
658 B
Rust
//! Records every `TrapCode` that cranelift outputs during code generation,
|
|
//! for every function in the module. This data may be useful at runtime.
|
|
|
|
use cranelift_codegen::{binemit, ir};
|
|
use cranelift_module::TrapSite;
|
|
|
|
/// Record of the trap sites for a given function
|
|
#[derive(Default, Clone)]
|
|
pub struct ObjectTrapSink {
|
|
/// All trap sites collected in function
|
|
pub sites: Vec<TrapSite>,
|
|
}
|
|
|
|
impl binemit::TrapSink for ObjectTrapSink {
|
|
fn trap(&mut self, offset: binemit::CodeOffset, srcloc: ir::SourceLoc, code: ir::TrapCode) {
|
|
self.sites.push(TrapSite {
|
|
offset,
|
|
srcloc,
|
|
code,
|
|
});
|
|
}
|
|
}
|