-
Notifications
You must be signed in to change notification settings - Fork 10.5k
Use toolchain clang on macOS #74033
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
Use toolchain clang on macOS #74033
Conversation
@swift-ci please test |
preset=asan |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
preset=asan |
preset=asan |
ff501c8
to
72e37c2
Compare
@swift-ci please test |
preset=asan |
preset=asan |
Ooohhh kay, so it appears that the combination of toolchain tools and just-built tools changes when building with ASAN vs not on Linux. 😭 Building normally Building with ASAN |
Don't use the just-built clang on macOS. macOS does this more "right" than the Linux build. Linux will sometimes use the just-built Swift-driver with the just-built clang, but sometimes would use the system clang instead. macOS uses the toolchain Swift-driver with the toolchain clang. This is correct, but it means that if we force the other clang, we'll get mismatched sanitizer runtimes so the ASAN bot will fail.
These two tests are exposing a use-after-free in the dependency scanner. Disabling them for now so that I can fix the ASAN bots. Disabled tests: - ScanDependencies/error_path.swift - ScanDependencies/error_source_locations.swift
72e37c2
to
a7432eb
Compare
preset=asan |
preset=asan |
I'm a bit confused about how the Linux ASAN ever worked. swiftcore is built with |
@swift-ci please test |
Don't use the just-built clang on macOS. macOS does this more "right" than the Linux build. Linux will sometimes use the just-built Swift-driver with the just-built clang, but sometimes would use the system clang instead. macOS uses the toolchain Swift-driver with the toolchain clang. This is correct, but it means that if we force the other clang, we'll get mismatched sanitizer runtimes so the ASAN bot will fail.
rdar://128602427