[build-script] Skip libLTO in sanitizer presets (#91274) - #91400
Open
duow310 wants to merge 1 commit into
Open
Conversation
On macOS, ld dlopens libLTO.dylib eagerly at startup to probe LTO capabilities. When the swift-built libLTO is sanitized, dyld pulls the sanitizer runtime into ld's process, and AMFI's sanitizer-load platform policy on recent macOS versions rejects it, aborting the link. Skip building libLTO in the sanitizer presets so ld falls back to Xcode's unsanitized copy; these presets don't exercise LTO codegen. (cherry picked from commit f3bea01) Signed-off-by: Duo Wang <duo_wang@apple.com>
Contributor
Author
|
@swift-ci smoke test |
shahmishal
approved these changes
Aug 11, 2026
Member
|
@swift-ci test |
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
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.
On macOS, ld dlopens libLTO.dylib eagerly at startup to probe LTO capabilities. When the swift-built libLTO is sanitized, dyld pulls the sanitizer runtime into ld's process, and AMFI's sanitizer-load platform policy on recent macOS versions rejects it, aborting the link. Skip building libLTO in the sanitizer presets so ld falls back to Xcode's unsanitized copy; these presets don't exercise LTO codegen.
This only affects the ASAN CI jobs.
Build failure in the new ASAN CI job being brought up.
[build-script] Skip libLTO in sanitizer presets #91274
Low. The ASAN preset does not exercise LTO so we lose little to no test coverage.
Tested in the new ASAN CI job being brought up.
@ndrewh