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

Detect loops & improved value tracking #53

Open
NaC-L opened this issue Jan 8, 2025 · 0 comments
Open

Detect loops & improved value tracking #53

NaC-L opened this issue Jan 8, 2025 · 0 comments

Comments

@NaC-L
Copy link
Owner

NaC-L commented Jan 8, 2025

Basically we can find loops if the jump is calculated in the edge between jump and jump location. However, as we currently propagate the values, some of the information is lost. So when calculating constants, we should also come up with a way to locate where the constant was calculated. As far as I know, constants are obtained with getOrCreateConstant, so they are not unique. Additionally, when we determine that we are in a loop, we can lift in "loop mode" without folding and with phi's. After we lift the loop, we should try to find loop invariant code, unroll certain variables and etc.

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