Transitions from DOUBLE to FAST were not checking for allocation site info.
authormvstanton@chromium.org <mvstanton@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Thu, 19 Sep 2013 09:48:50 +0000 (09:48 +0000)
committermvstanton@chromium.org <mvstanton@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Thu, 19 Sep 2013 09:48:50 +0000 (09:48 +0000)
commit59c32b64817064ba9e3aa048a2c7bf5c9c291a27
treecb1f803b24f938aac0a801415088ea4919e7be10
parentc57236e2889fb8e48b5f357c2522b34f8934170e
Transitions from DOUBLE to FAST were not checking for allocation site info.
This creates a confusing result. It's better to let allocation sites
transition to their end state than artificially stop tracking at the
double/fast boundary.

BUG=
R=verwaest@chromium.org

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

git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@16820 ce2b1a6d-e550-0410-aec6-3dcde31c8c00
src/objects.cc
test/mjsunit/allocation-site-info.js
test/mjsunit/array-literal-feedback.js