[Dependency Scan] Do not pass clang's -dwarf-debug-flags
to swift
#79179
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.
When turning on directCC1 scanning, swift will ask clang driver to expand all cc1 flags and pass that explicitly on command-line. In such case, if
RC_DEBUG_OPTIONS
env is set on darwin platform, it will cause clang driver to encode all the options it gets and pass those clang driver options as a cc1 options-dwarf-debug-flags
.After the change, swift scanner will no longer generate a long
-Xcc -dwarf-debug-flag -Xcc <long list of flags>
for later compilation. Losing such information in DWARF doesn't affect swift debugging. It will instead, make command-line a lot shorter, save spaces in swift binary module, and make swift caching build more reliable.rdar://144267483