On Jul 30, 2013, at 8:47 AM, Jussi Kalliokoski <jussi.kalliokoski@gmail.com> wrote: > Does this impose a performance cost on Float32Array access, BTW? I tried figuring it out on my own but I've been following leads in the WebKit source for a while and haven't found the code that does this. We re-used the high-order bit in ArrayBufferView's offset to track non-neuterableness. So yes, in that offset calculations now need to mask off that bit, but the cost is negligable. See: http://trac.webkit.org/browser/trunk/Source/WTF/wtf/ArrayBufferView.h#L134 http://trac.webkit.org/browser/trunk/Source/WTF/wtf/ArrayBuffer.cpp#L36 -Jer
Received on Tuesday, 30 July 2013 15:53:23 UTC