From: vegorov@chromium.org <vegorov@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Date: Thu, 7 Jul 2011 10:22:39 +0000 (+0000)
Subject: When resolving phies use ANY instead of NONE as a policy for phi operands.
X-Git-Tag: upstream/4.7.83~18957
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=c1e1e97b8b9a2f7596be70a088746122e9753205;p=platform%2Fupstream%2Fv8.git

When resolving phies use ANY instead of NONE as a policy for phi operands.

R=fschneider@chromium.org

Review URL: http://codereview.chromium.org/7313023

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@8562 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
---

diff --git a/src/lithium-allocator.cc b/src/lithium-allocator.cc
index dcdc5d9..4661106 100644
--- a/src/lithium-allocator.cc
+++ b/src/lithium-allocator.cc
@@ -1024,7 +1024,7 @@ void LAllocator::ResolvePhis(HBasicBlock* block) {
         operand = chunk_->DefineConstantOperand(constant);
       } else {
         ASSERT(!op->EmitAtUses());
-        LUnallocated* unalloc = new LUnallocated(LUnallocated::NONE);
+        LUnallocated* unalloc = new LUnallocated(LUnallocated::ANY);
         unalloc->set_virtual_register(op->id());
         operand = unalloc;
       }