-
Notifications
You must be signed in to change notification settings - Fork 14.1k
Make --print=backend-has-zstd work by default on any backend
#149764
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
base: main
Are you sure you want to change the base?
Conversation
|
r? @fee1-dead rustbot has assigned @fee1-dead. Use |
|
cc @bjorn3 |
|
Would you mind removing https://github.com/rust-lang/rust/pull/149776/files#diff-b5a09d09fd21f3236a6ae904132f826f38c29be9347281fc97de6792fe081df4R163-R172 in this PR once the subtree sync lands? |
|
This PR was rebased onto a different main commit. Here's a range-diff highlighting what actually changed. Rebasing is a normal part of keeping PRs up to date, so no action is needed—this note is just to help reviewers. |
Using a defaulted `CodegenBackend` method that querying for zstd support should automatically print a safe value of `false` on any backend that doesn't specifically indicate the presence or absence of zstd.
|
Removed the now-dead implementation of |
Using a defaulted
CodegenBackendmethod that querying for zstd support should automatically print a safe value offalseon any backend that doesn't specifically indicate the presence or absence of zstd.This should fix the compiletest failures reported in #149666 (comment), which can occur when LLVM is not the default codegen backend.