[Public WebGL] Differing TypedArray#set behavior

Oliver Hunt [email protected]
Thu Apr 12 14:06:39 PDT 2012


We allow the backing store to be replaced on a live/bound view?  I thought the was just for replacement of the buffer in the event the view had been neutered or initialised without a backing buffer.

If that's not the case we're essentially saying "typed arrays are important for performance, but lets make them as slow as possible"

--Oliver

On Apr 12, 2012, at 1:57 PM, Stéphan Kochen <[email protected]> wrote:

> 
> On Thursday 12 April 2012 at 20:22, Boris Zbarsky wrote:
>> So in your test, that should lead to a[0] == a[1] == 5, and the Firefox  
>> behavior is correct. Would you mind filing bugs on JSC and V8 and Opera  
>> here?
> 
> Okay, thanks for confirming.
> 
> There is no TypedArrays code in V8 itself, so I reported against Chrome instead:
> https://code.google.com/p/chromium/issues/detail?id=123216
> 
> The test also fails on a nightly of Webkit. Report is at:
> https://bugs.webkit.org/show_bug.cgi?id=83818
> 
> The test also fails on Opera Next (12). Reported, though it seems I can't link the issue.
> 
> --  
> Stéphan Kochen
> Two Screen, Angry Bytes
> 
> 
> 
> 
> -----------------------------------------------------------
> You are currently subscribed to [email protected]
> To unsubscribe, send an email to [email protected] with
> the following command in the body of your email:
> unsubscribe public_webgl
> -----------------------------------------------------------
> 


-----------------------------------------------------------
You are currently subscribed to [email protected]
To unsubscribe, send an email to [email protected] with
the following command in the body of your email:
unsubscribe public_webgl
-----------------------------------------------------------





More information about the public_webgl mailing list