diff options
| author | bors <bors@rust-lang.org> | 2025-01-26 09:26:34 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2025-01-26 09:26:34 +0000 |
| commit | 500614552d91e814ddf5f45ccfe085e00fa9990d (patch) | |
| tree | f989e561f9215b7001776cab57d901a58f3b8fd5 /compiler/rustc_codegen_llvm/src | |
| parent | 618062263053a24ff6a319a6bddf56fbcbe3a171 (diff) | |
| parent | 2b488c3e51c8cd810db13111ce4a75a774a100b9 (diff) | |
| download | rust-500614552d91e814ddf5f45ccfe085e00fa9990d.tar.gz rust-500614552d91e814ddf5f45ccfe085e00fa9990d.zip | |
Auto merge of #135753 - compiler-errors:from-ty-const, r=oli-obk
Get rid of `mir::Const::from_ty_const` This function is strange, because it turns valtrees into `mir::Const::Value`, but the rest of the const variants stay as type system consts. All of the callsites except for one in `instsimplify` (array length simplification of `ptr_metadata` call) just go through the valtree arm of the function, so it's easier to just create a `mir::Const` directly for those. For the instsimplify case, if we have a type system const we should *keep* having a type system const, rather than turning it into a `mir::Const::Value`; it doesn't really matter in practice, though, bc `usize` has no padding, but it feels more principled.
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions