On 28 March 2013 21:42, Mark S. Miller erig...@google.com wrote:
prohibitively depends on your tolerance. Modern machines can usually do
register-to-register byte order reversal rather speedily. Which big endian
machines do you have in mind?
For WebGL, which expects native endianness on its
On 28 March 2013 23:01, David Herman dher...@mozilla.com wrote:
On Mar 27, 2013, at 6:51 AM, Andreas Rossberg rossb...@google.com wrote:
There actually are (third-party) projects
with ports of V8 and/or Chromium to big endian architectures.
It would be helpful to have more information about
On Sun, Mar 31, 2013 at 1:42 PM, Kevin Gadd kevin.g...@gmail.com wrote:
One could also argue that people using typed arrays to alias and munge
individual values should be using DataView instead. If it performs poorly,
that can hopefully be addressed in the JS runtimes (the way it's specified
(Apologies for breaking threading -- subscribed too late to have
original message to reply to.)
David Herman wrote:
On Mar 27, 2013, at 6:51 AM, Andreas Rossberg rossberg at google.com
https://mail.mozilla.org/listinfo/es-discuss wrote:
/ There actually are (third-party) projects
// with
One could also argue that people using typed arrays to alias and munge
individual values should be using DataView instead. If it performs poorly,
that can hopefully be addressed in the JS runtimes (the way it's specified
doesn't seem to prevent it from being efficient).
-kg
On Sun, Mar 31, 2013
prohibitively depends on your tolerance. Modern machines can usually do
register-to-register byte order reversal rather speedily. Which big endian
machines do you have in mind?
On Wed, Mar 27, 2013 at 6:51 AM, Andreas Rossberg rossb...@google.comwrote:
On 27 March 2013 00:35, David Herman
On Mar 27, 2013, at 6:51 AM, Andreas Rossberg rossb...@google.com wrote:
There actually are (third-party) projects
with ports of V8 and/or Chromium to big endian architectures.
It would be helpful to have more information about what these platforms and
projects are.
WebGL
code should not
On Tue, Mar 26, 2013 at 4:35 PM, David Herman dher...@mozilla.com wrote:
[breaking out a new thread since this is orthogonal to the NaN issue]
While the Khronos spec never specified an endianness, TC39 agreed in May 2012
to make the byte order explicitly little-endian in ES6:
8 matches
Mail list logo