Revert of [runtime] Do not use the enum-cache for non-prototype objects.

Revert of [runtime] Do not use the enum-cache for non-prototype objects. (patchset #10 id:180001 of https://codereview.chromium.org/1608523002/ )

Reason for revert:
tanks for-in significantly

Original issue's description:
> [runtime] Do not use the enum-cache for keys retrieval.
>
> Currently we fail to properly handle shadowed properties. If the
> receiver defines a non-enumerable property that reappears on the
> prototype as enumerable it incorrectly shows up in [[Enumerate]].
> By extending the KeyAccumulator to track non-enumerable properties
> we can now properly filter them out when seeing them further up in
> the prototype-chain.
>
> BUG=v8:705
> LOG=y
>
> Committed: https://crrev.com/ed24dfe80d1da0827b8571839ee52c03ad09c9c7
> Cr-Commit-Position: refs/heads/master@{#33405}

TBR=jkummerow@chromium.org,bmeurer@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=v8:705
LOG=n

Committed: https://crrev.com/6e0573c6fff1c3041bab106d1197ab1b64aa9a6a
Cr-Commit-Position: refs/heads/master@{#33443}

[Camillo Bruni, 2016-01-21 17:22:55]

Created Revert of [runtime] Do not use the enum-cache for non-prototype objects.

[commit-bot: I haz the power, 2016-01-21 17:23:06]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1619803003/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1619803003/1

[commit-bot: I haz the power, 2016-01-21 17:25:22]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-01-21 17:25:23]

Try jobs failed on following builders:
  v8_presubmit on tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_presubmit/builds/10019)

[Jakob Kummerow, 2016-01-21 17:45:48]

Description was changed from

==========
Revert of [runtime] Do not use the enum-cache for non-prototype objects.
(patchset #10 id:180001 of https://codereview.chromium.org/1608523002/ )

Reason for revert:
tanks for-in significantly

Original issue's description:
> [runtime] Do not use the enum-cache for keys retrieval.
> 
> Currently we fail to properly handle shadowed properties. If the
> receiver defines a non-enumerable property that reappears on the
> prototype as enumerable it incorrectly shows up in [[Enumerate]].
> By extending the KeyAccumulator to track non-enumerable properties
> we can now properly filter them out when seeing them further up in
> the prototype-chain.
> 
> BUG=v8:705
> LOG=y
> 
> Committed: https://crrev.com/ed24dfe80d1da0827b8571839ee52c03ad09c9c7
> Cr-Commit-Position: refs/heads/master@{#33405}

TBR=jkummerow@chromium.org,bmeurer@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=v8:705
==========

to

==========
Revert of [runtime] Do not use the enum-cache for non-prototype objects.
(patchset #10 id:180001 of https://codereview.chromium.org/1608523002/ )

Reason for revert:
tanks for-in significantly

Original issue's description:
> [runtime] Do not use the enum-cache for keys retrieval.
> 
> Currently we fail to properly handle shadowed properties. If the
> receiver defines a non-enumerable property that reappears on the
> prototype as enumerable it incorrectly shows up in [[Enumerate]].
> By extending the KeyAccumulator to track non-enumerable properties
> we can now properly filter them out when seeing them further up in
> the prototype-chain.
> 
> BUG=v8:705
> LOG=y
> 
> Committed: https://crrev.com/ed24dfe80d1da0827b8571839ee52c03ad09c9c7
> Cr-Commit-Position: refs/heads/master@{#33405}

TBR=jkummerow@chromium.org,bmeurer@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=v8:705
LOG=n
==========

[Jakob Kummerow, 2016-01-21 17:45:54]

lgtm

[Jakob Kummerow, 2016-01-21 17:46:00]

The CQ bit was checked by jkummerow@chromium.org

[commit-bot: I haz the power, 2016-01-21 17:46:11]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1619803003/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1619803003/1

[commit-bot: I haz the power, 2016-01-21 17:48:02]

Description was changed from

==========
Revert of [runtime] Do not use the enum-cache for non-prototype objects.
(patchset #10 id:180001 of https://codereview.chromium.org/1608523002/ )

Reason for revert:
tanks for-in significantly

Original issue's description:
> [runtime] Do not use the enum-cache for keys retrieval.
> 
> Currently we fail to properly handle shadowed properties. If the
> receiver defines a non-enumerable property that reappears on the
> prototype as enumerable it incorrectly shows up in [[Enumerate]].
> By extending the KeyAccumulator to track non-enumerable properties
> we can now properly filter them out when seeing them further up in
> the prototype-chain.
> 
> BUG=v8:705
> LOG=y
> 
> Committed: https://crrev.com/ed24dfe80d1da0827b8571839ee52c03ad09c9c7
> Cr-Commit-Position: refs/heads/master@{#33405}

TBR=jkummerow@chromium.org,bmeurer@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=v8:705
LOG=n
==========

to

==========
Revert of [runtime] Do not use the enum-cache for non-prototype objects.
(patchset #10 id:180001 of https://codereview.chromium.org/1608523002/ )

Reason for revert:
tanks for-in significantly

Original issue's description:
> [runtime] Do not use the enum-cache for keys retrieval.
> 
> Currently we fail to properly handle shadowed properties. If the
> receiver defines a non-enumerable property that reappears on the
> prototype as enumerable it incorrectly shows up in [[Enumerate]].
> By extending the KeyAccumulator to track non-enumerable properties
> we can now properly filter them out when seeing them further up in
> the prototype-chain.
> 
> BUG=v8:705
> LOG=y
> 
> Committed: https://crrev.com/ed24dfe80d1da0827b8571839ee52c03ad09c9c7
> Cr-Commit-Position: refs/heads/master@{#33405}

TBR=jkummerow@chromium.org,bmeurer@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=v8:705
LOG=n
==========

[commit-bot: I haz the power, 2016-01-21 17:48:03]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-01-21 17:48:17]

Description was changed from

==========
Revert of [runtime] Do not use the enum-cache for non-prototype objects.
(patchset #10 id:180001 of https://codereview.chromium.org/1608523002/ )

Reason for revert:
tanks for-in significantly

Original issue's description:
> [runtime] Do not use the enum-cache for keys retrieval.
> 
> Currently we fail to properly handle shadowed properties. If the
> receiver defines a non-enumerable property that reappears on the
> prototype as enumerable it incorrectly shows up in [[Enumerate]].
> By extending the KeyAccumulator to track non-enumerable properties
> we can now properly filter them out when seeing them further up in
> the prototype-chain.
> 
> BUG=v8:705
> LOG=y
> 
> Committed: https://crrev.com/ed24dfe80d1da0827b8571839ee52c03ad09c9c7
> Cr-Commit-Position: refs/heads/master@{#33405}

TBR=jkummerow@chromium.org,bmeurer@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=v8:705
LOG=n
==========

to

==========
Revert of [runtime] Do not use the enum-cache for non-prototype objects.
(patchset #10 id:180001 of https://codereview.chromium.org/1608523002/ )

Reason for revert:
tanks for-in significantly

Original issue's description:
> [runtime] Do not use the enum-cache for keys retrieval.
>
> Currently we fail to properly handle shadowed properties. If the
> receiver defines a non-enumerable property that reappears on the
> prototype as enumerable it incorrectly shows up in [[Enumerate]].
> By extending the KeyAccumulator to track non-enumerable properties
> we can now properly filter them out when seeing them further up in
> the prototype-chain.
>
> BUG=v8:705
> LOG=y
>
> Committed: https://crrev.com/ed24dfe80d1da0827b8571839ee52c03ad09c9c7
> Cr-Commit-Position: refs/heads/master@{#33405}

TBR=jkummerow@chromium.org,bmeurer@chromium.org
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=v8:705
LOG=n

Committed: https://crrev.com/6e0573c6fff1c3041bab106d1197ab1b64aa9a6a
Cr-Commit-Position: refs/heads/master@{#33443}
==========

[commit-bot: I haz the power, 2016-01-21 17:48:17]

Patchset 1 (id:??) landed as
https://crrev.com/6e0573c6fff1c3041bab106d1197ab1b64aa9a6a
Cr-Commit-Position: refs/heads/master@{#33443}

[Michael Achenbach, 2016-01-22 08:08:39]

This revert leads to a reproducible deopt problem:
https://build.chromium.org/p/client.v8/builders/V8%20Deopt%20Fuzzer/builds/74...

[Jakob Kummerow, 2016-01-22 08:40:46]

On 2016/01/22 08:08:39, Michael Achenbach wrote:
> This revert leads to a reproducible deopt problem:
>
https://build.chromium.org/p/client.v8/builders/V8%20Deopt%20Fuzzer/builds/74...

Benedikt says he took care of that already.

[Camillo Bruni, 2016-01-22 09:06:06]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/1612413003/ by cbruni@chromium.org.

The reason for reverting is: the deopt issues have been taken care of by
benedikt.