Handle JavaScript accessors on the global object.
authorsgjesse@chromium.org <sgjesse@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 1 Jul 2009 11:20:33 +0000 (11:20 +0000)
committersgjesse@chromium.org <sgjesse@chromium.org@ce2b1a6d-e550-0410-aec6-3dcde31c8c00>
Wed, 1 Jul 2009 11:20:33 +0000 (11:20 +0000)
commit25405ddd9cc2adb97c575b98a274980309859301
tree88cda0d54707f30efaa0c229a5b26c3afe08160c
parent10489497c517790c6a033d7d6d418966a2d0027b
Handle JavaScript accessors on the global object.

With the new representation of the global object adding JavaScript accessors for a property after global inline caches was created for that property did not work property as the inline caches did not take the JavaScript accessor information (fixed array with two elements) that could be present in a global object property cell into account.

This is now fixed by changing the map for a global object when a JavaScript accessor is defined on it.

BUG=394
TEST=test\mjsunit\regress\regress-394.js
Review URL: http://codereview.chromium.org/150162

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