diff options
| author | bors <bors@rust-lang.org> | 2020-09-01 07:44:34 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2020-09-01 07:44:34 +0000 |
| commit | 6f1bbf5ee014cdad5d95f13266b177d89cc40d89 (patch) | |
| tree | c4f2e45d56b520c4cbadd2e37b45f046da8a716b /compiler/rustc_resolve/src | |
| parent | d9cd4a33f53689bc0847775669a14f666a138fd7 (diff) | |
| parent | 1663bfba02b7c1545a3c241b6b08cc9d9b97c475 (diff) | |
| download | rust-6f1bbf5ee014cdad5d95f13266b177d89cc40d89.tar.gz rust-6f1bbf5ee014cdad5d95f13266b177d89cc40d89.zip | |
Auto merge of #76071 - khyperia:configurable_to_immediate, r=eddyb
Make to_immediate/from_immediate configurable by backends `librustc_codegen_ssa` has the concept of an immediate vs. memory type, and `librustc_codegen_llvm` uses this distinction to implement `bool`s being `i8` in memory, and `i1` in immediate contexts. However, some of that implementation leaked into `codegen_ssa` when converting to/from immediate values. So, move those methods into builder traits, so that behavior can be configured by backends. This is useful if a backend is able to keep bools as bools, or, needs to do more trickery than just bools to bytes. (Note that there's already a large amount of things abstracted with "immediate types" - this is just bringing this particular thing in line to be abstracted as well) --- Pinging @eddyb since that's who I was talking about this change with when they suggested I submit a PR.
Diffstat (limited to 'compiler/rustc_resolve/src')
0 files changed, 0 insertions, 0 deletions
