Add frontend option -no-serialize-debugging-options #20555
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
By default, the frontend tries to figure out if the built module is likely to be distributed in some way, and uses that to decide whether to include options that help with debugging (such as local search paths). There's long been a -serialize-debugging-options that forces those options to be included even when it looks like a framework is being built, but the opposite has been absent until now. Note that both of these options are still /frontend/ options, not driver options, which means they could still change in the future. (I'd really like to get to a point where debugging doesn't need to sniff these options out from the module this way, but there are some complications we'd need to work out. Swift 1 expediency coming back to cause trouble again.) rdar://problem/37954803
|
@swift-ci Please test |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
By default, the frontend tries to figure out if the built module is likely to be distributed in some way, and uses that to decide whether to include options that help with debugging (such as local search paths). There's long been a -serialize-debugging-options that forces those options to be included even when it looks like a framework is being built, but the opposite has been absent until now.
Note that both of these options are still frontend options, not driver options, which means they could still change in the future. (I'd really like to get to a point where debugging doesn't need to sniff these options out from the module this way, but there are some complications we'd need to work out. Swift 1 expediency coming back to cause trouble again.)
rdar://problem/37954803