On 2015/05/06 16:53:23, binji wrote:
> I think the complexity of this is getting a bit out of hands. Could we
possibly
> have a separate design document which outlines what needs to be done?
>
> The document should describe at least the following:
>
> 1. Representation of SAB in v8.
>
> 2. Compilation of non-atomic accesses to SAB. (Probably just like normal
> accesses to AB, but if the SAB have different map as in the current
version,
one
> has to be careful about map checks/polymorphism in hydrogen and ICs.)
>
> 3. Compilation of atomic accesses to SAB. This should discuss all the
compilers:
> full code, hydrogen and turbofan. My guess is we would be fine with
having
> runtime functions for full code and hydrogen, but turbofan needs to have
> optimized version. This should also discuss architecture specific
details
(such
> as implementation on architectures without 64-bit atomic instructions).
>
> 4. Compilation of futexes.
>
> 5. Discussion of neutering and friends.
>
> 6. API design, interface to the rest of chrome.
>
> I am sure I am missing other important aspects.
Sorry for the confusion. You're right, it will be helpful to have an
implementation document. I'll write one up today.
Still a lot more to add, but here is the doc:
https://docs.google.com/document/d/17bWw19CozbeDitdZxXBA-_7IdUzwzXB6XptLAIcsD74/edit?usp=sharing
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.
