-
Notifications
You must be signed in to change notification settings - Fork 12
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
Martien.skippresched #230
Martien.skippresched #230
Conversation
SKipping is based on loop metadata
ada6613
to
c78fd16
Compare
// The pipeliner is usually disabled to give the postpipeliner a chance. | ||
// The prescheduler also clutters the view of the postpipeliner, so we skip | ||
// such blocks here. | ||
auto Skip = [](MachineBasicBlock *Block) { |
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.
What do you think about a command line option to disable this?
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.
We discussed that this is a user-pragma driven affair so that an option is not really necessary. Om second thought I perhaps add one anyway, so that we can easily assess the overall effect of prescheduling
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.
LGTM.
If we want to give the postpipeliner a chance on (bigger) loops that fall outside of the normal offloading criteria, we can add a disable pragma to which the pre-pipeliner responds. In that case we also want to disable the scheduler since its actions clutter the view of the postpipeliner