Reapply load ICs for nonexistent properties....

Reapply load ICs for nonexistent properties.

We need to be careful to check global property cells for the property
encountered during lookup.  Therefore, the ICs have to be specific to
the name of the property if global objects are involved.  In
principle, this means that we could get a large number of monomorphic
ICs for the same map if there is a global object in the prototype
chain.  However, since this is only done for normal load ICs and not
for keyed load ICs I do not expect this to be a problem.  I will
experiment with it once this goes in.

BUG=675
Committed: http://code.google.com/p/v8/source/detail?r=4426

[Erik Corry, 2010-04-15 09:38:09]

This LGTM but it would be nice to still share the load IC for all the cases
where there is no global object involved.

[Mads Ager (chromium), 2010-04-15 10:05:42]

On 2010/04/15 09:38:09, Erik Corry wrote:
> This LGTM but it would be nice to still share the load IC for all the cases
> where there is no global object involved.

I agree and it is easy to do.  I have updated the change to do just that.  Could
you have a look at the latest patch set?

[Erik Corry, 2010-04-15 10:28:44]

STV!

http://codereview.chromium.org/1559033/diff/2002/17008
File src/arm/stub-cache-arm.cc (right):

http://codereview.chromium.org/1559033/diff/2002/17008#newcode1437
src/arm/stub-cache-arm.cc:1437: // Return undefined if maps of the full
prototype chain is still the
maps ... is -> maps ... are

http://codereview.chromium.org/1559033/diff/2002/17005
File src/ic.cc (right):

http://codereview.chromium.org/1559033/diff/2002/17005#newcode697
src/ic.cc:697: // Bail out if the result is not cachable.
http://www.googlefight.com/index.php?lang=en_GB&word1=cacheable&word2=cachable