diff options
| author | bors <bors@rust-lang.org> | 2024-03-01 03:36:11 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2024-03-01 03:36:11 +0000 |
| commit | fb18033b83b375589d37ed5e6768cac6ca8ef244 (patch) | |
| tree | e31f2024cde85d9c1071aaa724ee3f0698f261c8 /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp | |
| parent | 14b72519c948be0dc2f8caf6c843c54d34f1a184 (diff) | |
| parent | 17930c961458e741582e579bb91080936941ccdc (diff) | |
| download | rust-fb18033b83b375589d37ed5e6768cac6ca8ef244.tar.gz rust-fb18033b83b375589d37ed5e6768cac6ca8ef244.zip | |
Auto merge of #121728 - tgross35:f16-f128-step1-ty-updates, r=compiler-errors
Add stubs in IR and ABI for `f16` and `f128` This is the very first step toward the changes in https://github.com/rust-lang/rust/pull/114607 and the [`f16` and `f128` RFC](https://rust-lang.github.io/rfcs/3453-f16-and-f128.html). It adds the types to `rustc_type_ir::FloatTy` and `rustc_abi::Primitive`, and just propagates those out as `unimplemented!` stubs where necessary. These types do not parse yet so there is no feature gate, and it should be okay to use `unimplemented!`. The next steps will probably be AST support with parsing and the feature gate. r? `@compiler-errors` cc `@Nilstrieb` suggested breaking the PR up in https://github.com/rust-lang/rust/pull/120645#issuecomment-1925900572
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions