[turbofan] Create ExplicitOperands to specify operands without virtual registers

test/unittests/compiler/move-optimizer-unittest.cc

Index: test/unittests/compiler/move-optimizer-unittest.cc
diff --git a/test/unittests/compiler/move-optimizer-unittest.cc b/test/unittests/compiler/move-optimizer-unittest.cc
index fb2b6ad45739ac76ce1c3e685530243a080d1479..c1bae7d33fa42f5e72a476b77388e38c07a225c7 100644
--- a/test/unittests/compiler/move-optimizer-unittest.cc
+++ b/test/unittests/compiler/move-optimizer-unittest.cc
@@ -67,10 +67,12 @@ class MoveOptimizerTest : public InstructionSequenceTest {
       case kConstant:
         return ConstantOperand(op.value_);
       case kFixedSlot:
-        return StackSlotOperand(kRepWord32, op.value_);
+        return AllocatedOperand(LocationOperand::STACK_SLOT, kRepWord32,
+                                op.value_);
       case kFixedRegister:
         CHECK(0 <= op.value_ && op.value_ < num_general_registers());
-        return RegisterOperand(kRepWord32, op.value_);
+        return AllocatedOperand(LocationOperand::REGISTER, kRepWord32,
+                                op.value_);

[Mircea Trofin, 2015/10/15 15:05:38]

Should we also have a unit test where the move optimizer encounters an
ExplicitOperand?

[danno, 2015/10/23 08:07:49]

Done

       default:
         break;
     }