-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Disable new pass manager by default for the s390x targets. #89662
Disable new pass manager by default for the s390x targets. #89662
Conversation
r? @nagisa (rust-highfive has picked a reviewer for you, use r? to override) |
|
The job Click to see the possible cause of the failure (guessed by this bot)
|
Closing in favor of #89666. I did not realize that adding a field to the target spec would make it public contract. As this is only meant as a stop-gap measure exposing that is not a good idea. |
The target specification schema isn't considered a stable interface, but this seems like a bug that we'd like to fix either way so having an option to change this through a target seems unnecessary. |
With this change target specifications can opt in to provide a default setting for using the new LLVM pass manager via
TargetOptions::new_llvm_pass_manager
. In this PR it is only set toSome(false)
for s390x, disabling the new pass manager due to some major performance problems with it (see #89609).If no default is specified
rustc_codegen_llvm::back::write::should_use_new_llvm_pass_manager()
continues to enable the new pass manager iff the LLVM version is 13 or higher.The command line option
-Z new-llvm-pass-manager=(yes|no)
continues to override default values and should_use_new_llvm_pass_manager() logic.This is meant as a temporary measure until the problems with s390x are fixed.