Skip to content
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

Revert "[7.4.0] Fix ml path for Windows clang-cl cc toolchain (#23406)" #24211

Merged

Conversation

meteorcloudy
Copy link
Member

@meteorcloudy meteorcloudy commented Nov 5, 2024

This reverts commit cb1bc28.

Closes #24158

Related #24152

@meteorcloudy meteorcloudy requested a review from a team as a code owner November 5, 2024 12:17
@meteorcloudy meteorcloudy enabled auto-merge (squash) November 5, 2024 12:17
@github-actions github-actions bot added awaiting-review PR is awaiting review from an assigned reviewer team-Rules-CPP Issues for C++ rules labels Nov 5, 2024
@meteorcloudy meteorcloudy merged commit bcc4e9f into bazelbuild:release-7.4.1 Nov 5, 2024
51 checks passed
@github-actions github-actions bot removed the awaiting-review PR is awaiting review from an assigned reviewer label Nov 5, 2024
fhanau added a commit to fhanau/rules_cc that referenced this pull request Nov 11, 2024
This essentially reverts bazelbuild/bazel#23337 now that the toolchain
configuration has been moved here. clang-cl does support assembly just like
other clang variants and unlike MASM supports assembly using native AT&T syntax
as with regular clang. MSVC-style assembly requires using MASM, which continues
to be available in the MSVC toolchain.

This has previously been discussed in bazelbuild/bazel#24152 and reverted for
Bazel 7.4.1 in bazelbuild/bazel#24211. Ideally, we'd want to have some mechanism
to make assembler selection configurable and support several kinds of asm syntax
in the future.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
team-Rules-CPP Issues for C++ rules
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants