Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Updating stack space requirements of Tier 2 trace #50

Open
2 tasks done
JuliaPoo opened this issue Oct 26, 2023 · 0 comments
Open
2 tasks done

Updating stack space requirements of Tier 2 trace #50

JuliaPoo opened this issue Oct 26, 2023 · 0 comments

Comments

@JuliaPoo
Copy link
Collaborator

JuliaPoo commented Oct 26, 2023 •
edited
Loading

This issue just tracks progress and what needs to be done

Problem is that once a trace passes through the optimiser, the stack requirements are different.

Proposal:

  1. Add guard to check if the bump allocator has space for a new frame at every PUSH_FRAME
  2. If required, add ADJUST_STACK that precedes PUSH_FRAME if the stack of the frame is too small

Intermediate issues:

  • Identity currently labeled "guards" that can't be hoisted and make them impure
  • Support size operands for impure instructions in abstract interp. Is required to even test traces with PUSH_FRAME.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@JuliaPoo