-
Notifications
You must be signed in to change notification settings - Fork 98
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
Pipeline revng passes #348
Conversation
57fa58c
to
c242eeb
Compare
c242eeb
to
08f05de
Compare
AU.addRequired<LoadModelWrapperPass>(); | ||
AU.addRequired<pipeline::LoadExecutionContextPass>(); |
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.
Why do we still need LoadModelWrapperPass
?
We can get the model from the ExecutionContext
, can't we?
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.
yes, but we need to schedule LOadModelWrapperPAss anyway so people can do both. Do we wish to have a policy about this? in principle we could even entirely drop LoadModelWrapperPass
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 looked into this, but the change was sprawling and it still requires to make sure that revng opt is never used. I recommend to do it after after that issue is fixed
443675e
to
c21dc30
Compare
c21dc30
to
040829d
Compare
Propagates the deduced info about inputs and outputs of pipes all the way up to the runner, so that the requested output of a pipe can be passed to its invokation
040829d
to
31a5432
Compare
Closing this due to the heavy reworking I'm doing on this branch. |
No description provided.