Fix issue 294 by ensuring that we don't lose the copy flag on memory
authorkmillikin@chromium.org <kmillikin@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 31 Mar 2009 14:01:25 +0000 (14:01 +0000)
committerkmillikin@chromium.org <kmillikin@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 31 Mar 2009 14:01:25 +0000 (14:01 +0000)
commitc80b013999b3cfe70823133c14c97c741975f3d8
treec8f16c1907658f0be17f576f2fc2086e129d62ac
parent5829acb0959b862d32402c9ad593cbb108b0e706
Fix issue 294 by ensuring that we don't lose the copy flag on memory
frame elements when allocating them to a register as a result of
popping one of their copies.
Review URL: http://codereview.chromium.org/57053

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@1655 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/virtual-frame-ia32.cc
test/mjsunit/regress/regress-294.js [new file with mode: 0644]