Skip to content

bugc: update invoke contexts per spec fix (#207)#209

Merged
gnidan merged 4 commits intocall-returnfrom
compiler-update-invoke-pointers
Apr 2, 2026
Merged

bugc: update invoke contexts per spec fix (#207)#209
gnidan merged 4 commits intocall-returnfrom
compiler-update-invoke-pointers

Conversation

@gnidan
Copy link
Copy Markdown
Member

@gnidan gnidan commented Apr 2, 2026

Summary

  • Callee JUMPDEST gets full invoke context with arg pointers and code target
  • Caller JUMP simplified to identity + code target only (no arg pointers)
  • Target pointers changed from stack to code location, resolved at module-level patching via function registry

gnidan added 2 commits April 2, 2026 08:41
- Callee JUMPDEST: full invoke with arg pointers and code
  target (resolved at module-level patching)
- Caller JUMP: identity + code target only, no arg pointers
- Target pointers changed from stack to code location
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented Apr 2, 2026

PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-04-02 14:50 UTC

gnidan added 2 commits April 2, 2026 08:54
The invoke spec change moved argument pointers from the
caller JUMP to the callee entry JUMPDEST. The call stack
builder was updating argumentPointers from the duplicate
callee step but not argumentNames, causing names to show
as _0 instead of the actual parameter name.
Same fix as the programs-react mockTrace.ts change — the
duplicated call stack builder in TraceDrawer.tsx also needs
to update argumentNames from the callee entry step, not
just argumentPointers.
@gnidan gnidan merged commit 31e0973 into call-return Apr 2, 2026
4 checks passed
@gnidan gnidan deleted the compiler-update-invoke-pointers branch April 2, 2026 14:46
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.

1 participant