From c1e1e97b8b9a2f7596be70a088746122e9753205 Mon Sep 17 00:00:00 2001 From: "vegorov@chromium.org" Date: Thu, 7 Jul 2011 10:22:39 +0000 Subject: [PATCH] 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 --- src/lithium-allocator.cc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/lithium-allocator.cc b/src/lithium-allocator.cc index dcdc5d9b7d..466110678a 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; }