about summary refs log tree commit diff
path: root/compiler/rustc_codegen_gcc
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2024-03-01 03:36:11 +0000
committerbors <bors@rust-lang.org>2024-03-01 03:36:11 +0000
commit27b669adc2cbe4ec8cfae686d495f6a30a33096b (patch)
tree25b408d64bd4c97c196f2cb81c2e53c9233026fb /compiler/rustc_codegen_gcc
parent427d6176c5856b0edeb33c46633c8d8acf97affb (diff)
parent8dd96baddff3903a695a20d0e12ed92b3d2e435c (diff)
downloadrust-27b669adc2cbe4ec8cfae686d495f6a30a33096b.tar.gz
rust-27b669adc2cbe4ec8cfae686d495f6a30a33096b.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_codegen_gcc')
0 files changed, 0 insertions, 0 deletions