Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commit 57481e7

Browse files
committed
clif: Don't set the compiler-builtins-no-f16-f128 feature
Since rust-lang/rust be35d37 ("Use the compiler to determine whether or not to enable f16 and f128"), `compiler-builtins` relies on `rustc` to report whether or not `f16` and `f128` are supported, which is reported by the backend. This means that there should no longer be any need to unconditionally disable the types for clif in Bootstrap. Backend config: https://github.com/rust-lang/rust/blob/a955f1cd09a027363729ceed919952d09f76f28e/compiler/rustc_codegen_cranelift/src/lib.rs#L224-L233
1 parent a955f1c commit 57481e7

File tree

1 file changed

+0
-5
lines changed

1 file changed

+0
-5
lines changed

‎src/bootstrap/src/core/build_steps/compile.rs‎

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -597,11 +597,6 @@ pub fn std_cargo(builder: &Builder<'_>, target: TargetSelection, stage: u32, car
597597

598598
let mut features = String::new();
599599

600-
if stage != 0 && builder.config.default_codegen_backend(target).as_deref() == Some("cranelift")
601-
{
602-
features += "compiler-builtins-no-f16-f128 ";
603-
}
604-
605600
if builder.no_std(target) == Some(true) {
606601
features += " compiler-builtins-mem";
607602
if !target.starts_with("bpf") {

0 commit comments

Comments
(0)

AltStyle によって変換されたページ (->オリジナル) /