Semirandom changes in the code generated by gcc -g mean we can't iterate quite
authorerik.corry@gmail.com <erik.corry@gmail.com@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Mon, 15 Jun 2009 13:50:07 +0000 (13:50 +0000)
committererik.corry@gmail.com <erik.corry@gmail.com@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Mon, 15 Jun 2009 13:50:07 +0000 (13:50 +0000)
commit622e13f5731254fd91e41d1415815b208473e299
tree17cc65724c91a54897625c0dd800e827def4981e
parentb898b6dfea15c094fd089a273720708266f7b306
Semirandom changes in the code generated by gcc -g mean we can't iterate quite
as deep on newer VMs in debug mode.
Review URL: http://codereview.chromium.org/126125

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@2170 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
test/mjsunit/big-object-literal.js