-
Notifications
You must be signed in to change notification settings - Fork 217
Adds IR level PGO Instrumentation options #1992
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -243,6 +243,11 @@ extension Driver { | |
| try commandLine.appendLast(.RpassMissedEQ, from: &parsedOptions) | ||
| try commandLine.appendLast(.suppressWarnings, from: &parsedOptions) | ||
| try commandLine.appendLast(.profileGenerate, from: &parsedOptions) | ||
| try commandLine.appendLast(.irProfileGenerate, from: &parsedOptions) | ||
| try commandLine.appendLast(.irProfileGenerateEQ, from: &parsedOptions) | ||
| try commandLine.appendLast(.irProfileUse, from: &parsedOptions) | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is a flag that points to the file. It needs path remapping if needed. Use Also means this is not handled correctly in swift-frontend/scanner. See the comment I added to the other review.
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks @cachemeifyoucan for looking into it. Are you suggesting something as follows On trying the above, I get a fatalError in CommandLineArguments.appendFlag function I think the option
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hey @cachemeifyoucan / @drodriguez ,
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't understand the why of the request from @cachemeifyoucan . I cannot help with that. I think
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Thanks @drodriguez , I share the same understanding.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @cachemeifyoucan should it be done as part of this PR or as part of a follow up PR, since
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Please address it here if there is no good reason. You can do it in separate commit, but it is not something you can drop on the ground and let it break for days.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @cachemeifyoucan it has been "broken" for a couple of years for
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Sorry, I thought you always meant Please file an issue about missing caching support for both profile usage. I just checked that both profile usages don't work with swift caching even from swift-frontend side so there are more works to do in the compiler before swift-driver can make it possible to work.
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That said. I no longer block this change once we have the GitHub issue to tracking the missing feature. |
||
| try commandLine.appendLast(.csProfileGenerate, from: &parsedOptions) | ||
| try commandLine.appendLast(.csProfileGenerateEQ, from: &parsedOptions) | ||
| try commandLine.appendLast(.profileUse, from: &parsedOptions) | ||
| try commandLine.appendLast(.profileCoverageMapping, from: &parsedOptions) | ||
| try commandLine.appendLast(.debugInfoForProfiling, from: &parsedOptions) | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.