[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] How does WebGL 2 deal with GLint64 type?

And in Chrome, currently our command buffer supports only 32 bit, so
any GLint64 parameters that receives a value that exceeds 32bit, you
get an INVALID_VALUE error.

On Wed, Sep 9, 2015 at 1:25 PM, Jeff Gilbert <jgilbert@mozilla.com> wrote:
> We follow what the webidl types are spec'd to do, which I believe is
> practically just converting js::Number <-> GLint64. Accuracy suffers past
> 2^53, but that's true of all math in JS.
> On Wed, Sep 9, 2015 at 7:24 AM, Jukka Jylänki <jujjyl@gmail.com> wrote:
>> Reading the current WebGL 2 spec at
>> https://www.khronos.org/registry/webgl/specs/latest/2.0/ , it introduces a
>> new type GLint64.
>> How does that behave when JavaScript does not currently(yet) have a 64-bit
>> int value type?
>> Cheers,
>>    Jukka

You are currently subscribed to public_webgl@khronos.org.
To unsubscribe, send an email to majordomo@khronos.org with
the following command in the body of your email:
unsubscribe public_webgl