[turbofan] Create ExplicitOperands to specify operands without virtual registers

test/unittests/compiler/register-allocator-unittest.cc

Index: test/unittests/compiler/register-allocator-unittest.cc
diff --git a/test/unittests/compiler/register-allocator-unittest.cc b/test/unittests/compiler/register-allocator-unittest.cc
index c5ff90f301ec2ecc6165c57d997412b0a2adbe14..113a88873586f359ee91beae89311132128a0b20 100644
--- a/test/unittests/compiler/register-allocator-unittest.cc
+++ b/test/unittests/compiler/register-allocator-unittest.cc
@@ -41,8 +41,9 @@ bool AllocatedOperandMatches(
     const AllocatedOperand& op,
     const InstructionSequenceTest::TestOperand& test_op) {
   return AreOperandsOfSameType(op, test_op) &&
-         ((op.IsRegister() ? op.GetRegister().code() : op.index()) ==
-              test_op.value_ ||
+         ((op.IsRegister()
+               ? LocationOperand::cast(op).GetRegister().code()
+               : LocationOperand::cast(op).index()) == test_op.value_ ||
           test_op.value_ == InstructionSequenceTest::kNoValue);

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

Should we also have a unit test where the register allocator encounters an
ExplicitOperand?

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

The register allocator itself should never see ExplicitOperands, if it does it
will DCHECK fail when converting the ExplicitOperand to an AllocatedOperand.
I've changed this test to not use LocationOperand so that it's clear that only
AllocatedOperands are involved.

 }