Crate cranelift_codegen

Source
Expand description

Cranelift code generation library.

Re-exports§

  • pub use crate::verifier::verify_function;
  • pub use crate::write::write_function;
  • pub use cranelift_bforest as bforest;
  • pub use cranelift_bitset as bitset;
  • pub use cranelift_control as control;
  • pub use cranelift_entity as entity;
  • pub use gimli;
    unwind

Modules§

  • Binary machine code emission.
  • The CFGPrinter utility.
  • Cursor library.
  • This module gives users to instantiate values that Cranelift understands. These values are used, for example, during interpretation and for wrapping immediates.
  • Debug tracing helpers.
  • A Dominator Tree represented as mappings of Blocks to their immediate dominator.
  • A control flow graph represented as mappings of basic blocks to their predecessors and successors.
  • incremental_cacheincremental-cache
    This module provides a set of primitives that allow implementing an incremental cache on top of Cranelift, making it possible to reuse previous compiled artifacts for functions that have been compiled previously.
  • Representation of Cranelift IR functions.
  • Instruction Set Architectures.
  • A loop analysis represented as mappings of loops to their header Block and parent in the loop tree.
  • Compact representation of Option<T> for types with a reserved value.
  • Utility routines for pretty-printing error messages.
  • Shared settings module.
  • Pass timing.
  • Traversals over the IR.
  • A verifier for ensuring that functions are well formed. It verifies:
  • Converting Cranelift IR to text.

Macros§

  • Even when trace logging is disabled, the trace macro has a significant performance cost so we disable it by default.

Structs§

  • Out-of-line data for calls, to keep the size of Inst down.
  • Compilation error, with the accompanying function to help printing it.
  • Persistent data structures and compilation pipeline.
  • Status of a compiled artifact ready to use.
  • A buffer of output to be produced, fixed up, and then emitted to a CodeSink in bulk.
  • A MachBuffer once emission is completed: holds generated code and records, without fixups. This allows the type to be independent of the backend.
  • A call site record resulting from a compilation.
  • A label refers to some offset in a MachBuffer. It may not be resolved at the point at which it is used by emitted code; the buffer records “fixups” for references to the label, and will come back and patch the code appropriately when the label’s location is eventually known.
  • A source-location mapping resulting from a compilation.
  • Implementation of the TextSectionBuilder trait backed by MachBuffer.
  • A trap record resulting from a compilation.
  • Represents the beginning of an editable region in the MachBuffer, while code emission is still occurring. An OpenPatchRegion is closed by MachBuffer::end_patchable, consuming the OpenPatchRegion token in the process.
  • A region in the MachBuffer code buffer that can be edited prior to finalization. An example of where you might want to use this is for patching instructions that mention constants that won’t be known until later: MachBuffer::start_patchable can be used to begin the patchable region, instructions can be emitted with placeholder constants, and the PatchRegion token can be produced by MachBuffer::end_patchable. Once the values of those constants are known, the PatchRegion::patch function can be used to get a mutable buffer to the instruction bytes, and the constants uses can be updated directly.
  • A real (physical) register. This corresponds to one of the target ISA’s named registers and can be used as an instruction operand.
  • A register named in an instruction. This register can be either a virtual register or a fixed physical register. It does not have any constraints applied to it: those can be added later in MachInst::get_operands() when the Regs are converted to Operands.
  • This structure tracks the large constants used in VCode that will be emitted separately by the MachBuffer.
  • Value location range.
  • A type wrapper that indicates a register type is writable. The underlying register can be extracted, and the type wrapper can be built using an arbitrary register. Hence, this type-level wrapper is not strictly a guarantee. However, “casting” to a writable register is an explicit operation for which we can audit. Ordinarily, internal APIs in the compiler backend should take a Writable<Reg> whenever the register is written, and the usual, frictionless way to get one of these is to allocate a new temporary.

Enums§

Constants§

  • Version number of this crate.

Traits§

  • A machine instruction.
  • A trait describing the ability to encode a MachInst into binary machine code.
  • A trait describing the emission state carried between MachInsts when emitting a function body.
  • An object that can be used to create the text section of an executable.

Type Aliases§

  • A convenient alias for a Result that uses CodegenError as the error type.
  • CompiledCode in its final form (i.e. after FunctionParameters have been applied), ready for consumption.
  • A relocation resulting from a compilation.
  • Resulting map of Value labels and their ranges/locations.