Revert of [typedarrays] remove invalid optimization in NAMEConstructor()

Revert of [typedarrays] remove invalid optimization in NAMEConstructor() (patchset #1 id:1 of https://codereview.chromium.org/2544503002/ )

Reason for revert:
Speculative revert for causing timeouts on Win Debug gpu fyi bot

Nothing else looks even remotely relevant in the list of changes.
Will reland if this doesn't fix the issues.

BUG=670396
Original issue's description:
> [typedarrays] remove invalid optimization in NAMEConstructor()
>
> Before, we were treating objects with the builtin ArrayValues iterator
> method as array-like, where the iterator would iterate through to the
> full length of the object.
>
> This optimization was not sound, because it does not ensure that the
> next method hasn't been modified. Even if it hasn't been modified,
> it's entirely possible to be modified during iteration. Thus, this
> optimization has been removed due to its observability.
>
> BUG=v8:5699
> R=littledan@chromium.org, cbruni@chromium.org
>
> Committed: https://crrev.com/77df8c67d9609ada3b7d79e8e6d33f198bbad5a1
> Cr-Commit-Position: refs/heads/master@{#41394}

TBR=cbruni@chromium.org,littledan@chromium.org,caitp@igalia.com
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=v8:5699
Committed: https://crrev.com/0ea4a542202d501c4e550474e89512532571f3a0
Cr-Commit-Position: refs/heads/master@{#41461}

[enne (OOO), 2016-12-01 22:15:15]

The CQ bit was checked by enne@chromium.org

[enne (OOO), 2016-12-01 22:15:16]

Created Revert of [typedarrays] remove invalid optimization in NAMEConstructor()

[commit-bot: I haz the power, 2016-12-01 22:15:29]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-01 22:15:30]

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

[commit-bot: I haz the power, 2016-12-01 22:15:31]

No L-G-T-M from a valid reviewer yet. 
CQ run can only be started by full committers or once the patch has
received an L-G-T-M from a full committer.
Even if an L-G-T-M may have been provided, it was from a non-committer,
_not_ a full super star committer.
Committers are members of the group "project-v8-committers".
Note that this has nothing to do with OWNERS files.

[enne (OOO), 2016-12-01 22:19:33]

The CQ bit was checked by enne@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-12-01 22:19:36]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-01 22:44:35]

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

[commit-bot: I haz the power, 2016-12-01 22:44:35]

Dry run: This issue passed the CQ dry run.

[Dan Ehrenberg, 2016-12-02 18:45:45]

The CQ bit was checked by littledan@chromium.org

[commit-bot: I haz the power, 2016-12-02 18:45:51]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-02 18:45:52]

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

[commit-bot: I haz the power, 2016-12-02 18:45:52]

No L-G-T-M from a valid reviewer yet. 
CQ run can only be started by full committers or once the patch has
received an L-G-T-M from a full committer.
Even if an L-G-T-M may have been provided, it was from a non-committer,
_not_ a full super star committer.
Committers are members of the group "project-v8-committers".
Note that this has nothing to do with OWNERS files.

[Dan Ehrenberg, 2016-12-02 18:46:13]

The CQ bit was checked by littledan@chromium.org

[Dan Ehrenberg, 2016-12-02 18:46:14]

lgtm

lgtm

Speculative revert--performance degradation may have caused test timeouts.

[commit-bot: I haz the power, 2016-12-02 18:46:21]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-12-02 18:48:17]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1480704373708670, "parent_rev":
"baea5f493d0e79c3b872a9196f1bca993fb98528", "commit_rev":
"dc912da7e52fdc121b396824e55a482fd45fc0cd"}

[commit-bot: I haz the power, 2016-12-02 18:48:24]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-12-02 18:48:42]

Description was changed from

==========
Revert of [typedarrays] remove invalid optimization in NAMEConstructor()
(patchset #1 id:1 of https://codereview.chromium.org/2544503002/ )

Reason for revert:
Speculative revert for causing timeouts on Win Debug gpu fyi bot

Nothing else looks even remotely relevant in the list of changes.
Will reland if this doesn't fix the issues.

BUG=670396

Original issue's description:
> [typedarrays] remove invalid optimization in NAMEConstructor()
> 
> Before, we were treating objects with the builtin ArrayValues iterator
> method as array-like, where the iterator would iterate through to the
> full length of the object.
> 
> This optimization was not sound, because it does not ensure that the
> next method hasn't been modified. Even if it hasn't been modified,
> it's entirely possible to be modified during iteration. Thus, this
> optimization has been removed due to its observability.
> 
> BUG=v8:5699
> R=littledan@chromium.org, cbruni@chromium.org
> 
> Committed: https://crrev.com/77df8c67d9609ada3b7d79e8e6d33f198bbad5a1
> Cr-Commit-Position: refs/heads/master@{#41394}

TBR=cbruni@chromium.org,littledan@chromium.org,caitp@igalia.com
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=v8:5699
==========

to

==========
Revert of [typedarrays] remove invalid optimization in NAMEConstructor()
(patchset #1 id:1 of https://codereview.chromium.org/2544503002/ )

Reason for revert:
Speculative revert for causing timeouts on Win Debug gpu fyi bot

Nothing else looks even remotely relevant in the list of changes.
Will reland if this doesn't fix the issues.

BUG=670396

Original issue's description:
> [typedarrays] remove invalid optimization in NAMEConstructor()
>
> Before, we were treating objects with the builtin ArrayValues iterator
> method as array-like, where the iterator would iterate through to the
> full length of the object.
>
> This optimization was not sound, because it does not ensure that the
> next method hasn't been modified. Even if it hasn't been modified,
> it's entirely possible to be modified during iteration. Thus, this
> optimization has been removed due to its observability.
>
> BUG=v8:5699
> R=littledan@chromium.org, cbruni@chromium.org
>
> Committed: https://crrev.com/77df8c67d9609ada3b7d79e8e6d33f198bbad5a1
> Cr-Commit-Position: refs/heads/master@{#41394}

TBR=cbruni@chromium.org,littledan@chromium.org,caitp@igalia.com
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG=v8:5699

Committed: https://crrev.com/0ea4a542202d501c4e550474e89512532571f3a0
Cr-Commit-Position: refs/heads/master@{#41461}
==========

[commit-bot: I haz the power, 2016-12-02 18:48:43]

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

[ynovikov, 2016-12-05 20:58:40]

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

The reason for reverting is: The bot was not affected by the revert. Speculation
was wrong..