[5.9] Ensure module tracing is off when checking disable-implicit*
…
#68455
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.
…flags
In some internal configurations we set the
SWIFT_LOADED_MODULE_TRACE_FILE
environment variable when running the build of the compiler -- as a result, this causes-parse
to always fails, preventing to detect properly if we can usedisable-implicit*
flags.(cherry picked from commit ec49873)
Explanation: explicitly unset
SWIFT_LOADED_MODULE_TRACE_FILE
when detecting if the Swift compiler supporstdisable-implicit*
flags -- this is to prevent the-parse
invocation we use for such detection to fail unconditionallyRadar: rdar://115338219
Scope: build logic used to detect if the compiler supports
disable-implicit*
Risk: low
SWIFT_LOADED_MODULE_TRACE_FILE
is mostly used in internal configuration, and should not affect opensourceTesting: run a local Darwin build setting
SWIFT_LOADED_MODULE_TRACE_FILE
manually, checked that thedisable-implicit
flags are correctly used during builds of the compilerReviewed by: