v8/test/mjsunit/regress/regress-5018.js
adamk de7d47e22f 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

Review-Url: https://codereview.chromium.org/1984043002
Cr-Commit-Position: refs/heads/master@{#36382}
2016-05-19 19:49:35 +00:00

30 lines
740 B
JavaScript

// Copyright 2016 the V8 project authors. All rights reserved.
// Use of this source code is governed by a BSD-style license that can be
// found in the LICENSE file.
var dv = new DataView(new ArrayBuffer(4), 2);
function getByteLength(a) {
return a.byteLength;
}
assertEquals(2, getByteLength(dv));
assertEquals(2, getByteLength(dv));
Object.defineProperty(dv.__proto__, 'byteLength', {value: 42});
assertEquals(42, dv.byteLength);
assertEquals(42, getByteLength(dv));
function getByteOffset(a) {
return a.byteOffset;
}
assertEquals(2, getByteOffset(dv));
assertEquals(2, getByteOffset(dv));
Object.defineProperty(dv.__proto__, 'byteOffset', {value: 42});
assertEquals(42, dv.byteOffset);
assertEquals(42, getByteOffset(dv));