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.

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

Optimize the resulting code object. #2

Open
brandtbucher opened this issue Oct 16, 2019 · 1 comment
Open

Optimize the resulting code object. #2

brandtbucher opened this issue Oct 16, 2019 · 1 comment

Comments

@brandtbucher
Copy link
Owner

Currently, the code object we generate has too big of a stack, extra names/constants, and a ton of NOPs. We should take a page out of peephole.c’s playbook and optimize this stuff. We do need to be careful, though, to not change any of the legitimate generated instructions (including user-specified NOPs, which could be tricky).

Because this would make jumps basically impossible to write, #1 would most likely need to happen first.

@brandtbucher brandtbucher changed the title Optimize the resulting code object. Optimize the resulting code object further. Oct 25, 2019
@brandtbucher
Copy link
Owner Author

This is mostly done! All that's left is compressing lnotab, and being smarter about our stack size calculations.

@brandtbucher brandtbucher changed the title Optimize the resulting code object further. Optimize the resulting code object. Oct 25, 2019
@brandtbucher brandtbucher self-assigned this Dec 18, 2020
@brandtbucher brandtbucher removed their assignment Nov 18, 2022
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

No branches or pull requests

1 participant