Ross McIlroy b967c0d138 [Turboprop] Avoid using SAME_INPUT_OUTPUT registers for USED_AT_END inputs. ... If a register is used for both input and output by a SAME_INPUT_OUTPUT operand, then it represents a different virtual register for the end use-position of an instruction (since that will become the output's virtual register). It therefore can't be used to represent the input virtual register for any input operands that are USED_AT_END. BUG=chromium:1163715,v8:9684 Change-Id: I8dc0008ba81d5f1d0e38091b6dc013725c62b1b4 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2632700 Reviewed-by: Santiago Aboy Solanes <solanes@chromium.org> Commit-Queue: Ross McIlroy <rmcilroy@chromium.org> Cr-Commit-Position: refs/heads/master@{#72149}		2021-01-19 12:36:18 +00:00
..
live-range-unittest.cc	[regalloc] Remove live range splintering	2020-09-28 16:45:35 +00:00
mid-tier-register-allocator-unittest.cc	[Turboprop] Avoid using SAME_INPUT_OUTPUT registers for USED_AT_END inputs.	2021-01-19 12:36:18 +00:00
move-optimizer-unittest.cc	[turbofan][cleanup] Remove dead ExplicitOperand class.	2019-09-10 08:23:40 +00:00
register-allocator-unittest.cc	[regalloc] Remove live range splintering	2020-09-28 16:45:35 +00:00