On 2015/04/29 at 04:45:19, jarin wrote:
On 2015/04/28 19:42:09, jochen wrote:
> On 2015/04/28 at 19:39:05, dslomov wrote:
> > On 2015/04/28 18:31:46, jochen wrote:
> > > some comments
> > >
> > > it's unfortunate that the shared thingies have a different map -
that
means
> that
> > > code that handles both regular and shared typed arrays will go
polymorphic
> (i.e.
> > > ultra slow)
> >
> > Different maps (and having different code) is very much justified
here:
shared
> array buffer accesses MUST be different since they give memory model
guarantees.
>
> ok, but in the current patch, there's no difference yet..
SharedArrayBuffers should be only used in asm.js code and such code will
be
specialized for the specific buffer anyway, so that should not be a big
problem.
well, it's a full-blown language feature, so it has to work everywhere.
and ArrayBuffer.transfer is a "for-asm.js" feature... it's used for this
change
heap thing.
otoh, if you can't neuter them, then they shouldn't use the array buffer
code
that checks for neutering all over the place.
https://codereview.chromium.org/1069883002/
--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
---
You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
