diff options
| author | Jacob Pratt <jacob@jhpratt.dev> | 2025-07-26 22:42:39 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-07-26 22:42:39 -0400 |
| commit | d250b5cae4f83fa70ef756d708a33aee4a739125 (patch) | |
| tree | 9aaa8e747863811fb4f5218543ec5b779ad6c5d3 /tests/rustdoc-js-std/doc-alias-use.js | |
| parent | 2c0a33178190ff4e577afda2b89a535c4dc2dcf8 (diff) | |
| parent | 57481e791449a5510dab5c5c3ad1b4b3dd6ec30d (diff) | |
| download | rust-d250b5cae4f83fa70ef756d708a33aee4a739125.tar.gz rust-d250b5cae4f83fa70ef756d708a33aee4a739125.zip | |
Rollup merge of #144470 - tgross35:clif-remove-no-f16-f128, r=bjorn3
clif: Don't set the `compiler-builtins-no-f16-f128` feature
Since rust-lang/rust be35d37d8b6c ("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
Diffstat (limited to 'tests/rustdoc-js-std/doc-alias-use.js')
0 files changed, 0 insertions, 0 deletions