Fix gcstress test failure
authormvstanton@chromium.org <mvstanton@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 11 Feb 2014 09:06:13 +0000 (09:06 +0000)
committermvstanton@chromium.org <mvstanton@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Tue, 11 Feb 2014 09:06:13 +0000 (09:06 +0000)
commit95ad971d0f9a038bd2b38e893e2a8fa599ed32ac
tree03e56db1b24cf63a8b8575dce7749885ca9ce0ed
parentff5b05b662d33970c5caa8591e6d3955f518f14b
Fix gcstress test failure

Map collection complicates a test that wants to assert on code opt/deopt
because of prototype-chain changes. It can happen that a gc occurs
in the stack guard at the start of optimized function foo that deopts
function foo because of a map being collected and deoptimizing it's
dependent code.

R=bmeurer@chromium.org

Review URL: https://codereview.chromium.org/159653002

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@19258 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
test/mjsunit/getters-on-elements.js