Remove now-incorrect DataView accessor optimization

Remove now-incorrect DataView accessor optimization

In ES2015, the "byteLength" and "byteOffset" properties of DataViews are
getters on the prototype, so the previously-used strategy of special-casing
them using only the receiver map is invalid.

A future CL will need to use the same strategy which will be taken for
TypedArray "length", "byteLength", and "byteOffset": adding a prototype
chain check.

BUG=v8:5018, chromium:593634
Committed: https://crrev.com/de7d47e22f6296417300f712b3ff3d1a1cd6dba8
Cr-Commit-Position: refs/heads/master@{#36382}

[adamk, 2016-05-17 00:01:14]

adamk@chromium.org changed reviewers:
+ verwaest@chromium.org

[adamk, 2016-05-17 00:01:14]

Here's a warmup for our discussion tomorrow :)

[adamk, 2016-05-17 00:01:32]

Description was changed from

==========
Remove now-incorrect DataView accessor optimization

In ES2015, the "byteLength" and "byteOffset" properties of DataViews are
getters on the prototype, so the previously-used strategy of special-casing
them using only the receiver map is invalid.

A future CL will need to use the same strategy which will be taken for
TypedArray "length", "byteLength", and "byteOffset": adding a prototype
chain check.

BUG=v8:5018, chromium:593634
==========

to

==========
Remove now-incorrect DataView accessor optimization

In ES2015, the "byteLength" and "byteOffset" properties of DataViews are
getters on the prototype, so the previously-used strategy of special-casing
them using only the receiver map is invalid.

A future CL will need to use the same strategy which will be taken for
TypedArray "length", "byteLength", and "byteOffset": adding a prototype
chain check.

BUG=v8:5018, chromium:593634
==========

[Toon Verwaest, 2016-05-17 15:32:04]

lgtm

[adamk, 2016-05-18 19:31:45]

adamk@chromium.org changed reviewers:
+ mstarzinger@chromium.org

[adamk, 2016-05-18 19:31:45]

+mstarzinger for compiler/OWNERS

[Michael Starzinger, 2016-05-19 10:38:46]

LGTM on "compiler".

[adamk, 2016-05-19 19:18:25]

The CQ bit was checked by adamk@chromium.org

[commit-bot: I haz the power, 2016-05-19 19:18:33]

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

[commit-bot: I haz the power, 2016-05-19 19:48:04]

Description was changed from

==========
Remove now-incorrect DataView accessor optimization

In ES2015, the "byteLength" and "byteOffset" properties of DataViews are
getters on the prototype, so the previously-used strategy of special-casing
them using only the receiver map is invalid.

A future CL will need to use the same strategy which will be taken for
TypedArray "length", "byteLength", and "byteOffset": adding a prototype
chain check.

BUG=v8:5018, chromium:593634
==========

to

==========
Remove now-incorrect DataView accessor optimization

In ES2015, the "byteLength" and "byteOffset" properties of DataViews are
getters on the prototype, so the previously-used strategy of special-casing
them using only the receiver map is invalid.

A future CL will need to use the same strategy which will be taken for
TypedArray "length", "byteLength", and "byteOffset": adding a prototype
chain check.

BUG=v8:5018, chromium:593634
==========

[commit-bot: I haz the power, 2016-05-19 19:48:05]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-05-19 19:49:42]

Description was changed from

==========
Remove now-incorrect DataView accessor optimization

In ES2015, the "byteLength" and "byteOffset" properties of DataViews are
getters on the prototype, so the previously-used strategy of special-casing
them using only the receiver map is invalid.

A future CL will need to use the same strategy which will be taken for
TypedArray "length", "byteLength", and "byteOffset": adding a prototype
chain check.

BUG=v8:5018, chromium:593634
==========

to

==========
Remove now-incorrect DataView accessor optimization

In ES2015, the "byteLength" and "byteOffset" properties of DataViews are
getters on the prototype, so the previously-used strategy of special-casing
them using only the receiver map is invalid.

A future CL will need to use the same strategy which will be taken for
TypedArray "length", "byteLength", and "byteOffset": adding a prototype
chain check.

BUG=v8:5018, chromium:593634

Committed: https://crrev.com/de7d47e22f6296417300f712b3ff3d1a1cd6dba8
Cr-Commit-Position: refs/heads/master@{#36382}
==========

[commit-bot: I haz the power, 2016-05-19 19:49:43]

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