Skip to content

Wasm: add a profiling optimizing compiler #489

Description

@chrisbbreuer

Parent: #486
Depends on: #487, #469, #470, #481

Goal

Add a profiling optimizing WebAssembly tier for hot functions and loops, including bounds/alias/range optimization, inlining, and allocation/GC specialization.

Scope

No-workaround rules

  • No hoisting across a possible trap/effect when observable order changes, stale memory base after growth, lost integer wrap/NaN behavior, assumed import purity, or unbounded compile/code growth.

Acceptance

Foundation

Reuse the verified optimization/effect principles from #469, not JavaScript-specific value semantics.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestperformanceMeasured runtime, memory, scaling, or build performancewasmWebAssembly runtime, compilers, and benchmarks

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions