Skip to content

Introduce accumulator based interpreter architecture#1855

Draft
Robbepop wants to merge 45 commits into
mainfrom
rf-accumulator-based-interpreter-arch
Draft

Introduce accumulator based interpreter architecture#1855
Robbepop wants to merge 45 commits into
mainfrom
rf-accumulator-based-interpreter-arch

Conversation

@Robbepop
Copy link
Copy Markdown
Member

@Robbepop Robbepop commented May 7, 2026

Closes #1739.

ToDo: Definition, Translation & Execution

  • Keep track of Operand::Reg operands on the Stack
    • This is required in order to copy them to Operand::Temp when there are conflicts.
  • Operator Definition, Translation & Execution
    • Unary Ops
    • Binary Ops
      • Div/Rem
      • Copysign
      • Shift
      • All Others
    • Compare-Branch Ops
    • Load Ops
    • Store Ops
    • Simd Ops
    • Select Ops
    • Call Ops
    • Conversion Ops
    • Copy Ops
    • Return Ops
    • Memory Bulk Ops
    • Table Bulk Ops
    • Global Ops

Robbepop added 30 commits May 4, 2026 13:24
Parameters for register operands are not needed since they are a unit type and thus can be trivially default initialized.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Use accumulator-based interpreter architecture

1 participant