Cranelift, Part 3: Correctness in Register Allocation

This page summarizes the projects mentioned and recommended in the original post on /r/rust

Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
  • wasmtime

    A fast and secure runtime for WebAssembly

  • In a little more detail -- we handle register saves/restores in the ABI implementation which explicitly reasons about caller/callee-saves. The interaction with regalloc is actually kind of elegant IMHO: we just add all of the caller-save registers as defs on the call instruction. Regalloc.rs allows real (physical) registers alongside virtual registers in the VCode, and will see these defs and move other data out of the way.

  • reference-types

    Discontinued Proposal for adding basic reference types (anyref)

  • Re: GC -- yes, indeed, the whole business with safepoints arose from the need to support Wasm reference types as a backend for Wasmtime or Firefox. No safepoints are needed for Rust (or other C-like) code.

  • InfluxDB

    Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

    InfluxDB logo
NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a more popular project.

Suggest a related project

Related posts