Skip to content

[windows][toolchain] Restrict the sanitizer build to x64 and disable the legacy path for builtins #78011

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

Conversation

weliveindetail
Copy link
Member

Unfortunately, on Windows arm64 ASAN isn't working yet. These two changes should have a slightly positive effect on the CI runtime.

@@ -2774,7 +2774,9 @@ if (-not $SkipBuild) {

$InstallTo = "$($HostArch.ToolchainInstallRoot)\usr"
foreach ($Arch in $WindowsSDKArchs) {
Invoke-BuildStep Build-Sanitizers Windows $Arch $InstallTo
if ($Arch.ShortName = "x64") {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can the sanitizers work on x86 as well?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, but we didn't test it and since the arm64 test was negative, it seemed reasonable to stick to what we know works.

@compnerd
Copy link
Member

compnerd commented Dec 6, 2024

@swift-ci please test

@weliveindetail
Copy link
Member Author

Closing this PR. It landed as part of #77770

@weliveindetail weliveindetail deleted the windows-toolchain-sanitizers-followup branch January 23, 2025 10:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants