-
Notifications
You must be signed in to change notification settings - Fork 7
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
Refactoring jump targets and backedges to update inplace #83
base: main
Are you sure you want to change the base?
Conversation
Can this be rebased onto |
f04eeb9
to
adeeacf
Compare
adeeacf
to
d2331e7
Compare
Question: why was it necessary to remove the ability to deep-copy before application of any major algorithm? It should still be possible to deep-copy between closing, loop- and branch-restructure? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have given this a first pass and found some items to address.
It wasn't necessary to remove it, but rather it makes no difference for it to be there, since the graph is anyways mutable. Unless we have a fallback mechanism which I think is actually something we should look into. |
Co-authored-by: esc <esc@users.noreply.github.com>
Resolves: #73
Builds on top of #50
As an alternative to #58,
We can update the
jump_targets
andbackedges
within theBasicBlock
object to prevent copies and do minimal changes to code logic.