-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Use new dataflow framework for generators #69295
Use new dataflow framework for generators #69295
Conversation
This comment has been minimized.
This comment has been minimized.
2d2637a
to
5b89e0a
Compare
Ping @tmandry |
This comment has been minimized.
This comment has been minimized.
This is more ergonomic than importing `dataflow::visit_results`
...to be consistent with the naming of other dataflow analyses.
5b89e0a
to
75d256f
Compare
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.
Sorry for the delay on my end! It's been a wild couple of weeks.
Looks good, r=me after comment.
EDIT: The new framework looks really nice. :)
@bors r=tmandry |
📌 Commit dd69017f3f9a0e8e76ac6cfbfe8029250bf87270 has been approved by |
This comment has been minimized.
This comment has been minimized.
Reverse post-order requires an allocation.
dd69017
to
21cd1fe
Compare
Ugh, that was a bit loose. @bors r=tmandry |
📌 Commit 21cd1fe has been approved by |
☀️ Test successful - checks-azure |
#65672 introduced a new dataflow framework that can handle arbitrarily complex transfer functions as well as ones expressed as a series of gen/kill operations. This PR ports the analyses used to implement generators to the new framework so that we can remove the old one. See #68241 for a prior example of this. The new framework has some superficial API changes, but this shouldn't alter the generator passes in any way.
r? @tmandry