about summary refs log tree commit diff
path: root/compiler/rustc_codegen_llvm/src
diff options
context:
space:
mode:
authorGuillaume Gomez <guillaume1.gomez@gmail.com>2025-07-20 15:34:05 +0200
committerGitHub <noreply@github.com>2025-07-20 15:34:05 +0200
commit2461d6ccb893254011b117b1aa4e3340b07aa65d (patch)
tree71141e54253fde5e3fc30396b45c77d227215bf6 /compiler/rustc_codegen_llvm/src
parent5ba1251b55ed560aabf92c81db6a6612de5f648e (diff)
parent4b8f869c638e6d5090420ff46bd14e7b7d909690 (diff)
downloadrust-2461d6ccb893254011b117b1aa4e3340b07aa65d.tar.gz
rust-2461d6ccb893254011b117b1aa4e3340b07aa65d.zip
Rollup merge of #143720 - scottmcm:rvalue-always-operand, r=lcnr
Allow `Rvalue::Repeat` to return true in `rvalue_creates_operand` too

The conversation in https://github.com/rust-lang/rust/pull/143502#discussion_r2189410911 made be realize how easy this is to handle, since the only possibilty is ZSTs -- everything else ends up with the destination being `LocalKind::Memory` and thus doesn't call `codegen_rvalue_operand` at all.

This gets us perilously close to a world where `rvalue_creates_operand` only ever returns true.  (See rust-lang/rust#143860 for more.)
Diffstat (limited to 'compiler/rustc_codegen_llvm/src')
0 files changed, 0 insertions, 0 deletions