[Webkit-unassigned] [Bug 164653] New: We should make the contract of holding a lock while modifying a ByValInfo explicit in ByValInfo's API

[bugzilla-daemon at webkit.org]

https://bugs.webkit.org/show_bug.cgi?id=164653

            Bug ID: 164653
           Summary: We should make the contract of holding a lock while
                    modifying a ByValInfo explicit in ByValInfo's API
    Classification: Unclassified
           Product: WebKit
           Version: WebKit Nightly Build
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: JavaScriptCore
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: sbarati at apple.com
                CC: benjamin at webkit.org, fpizlo at apple.com,
                    ggaren at apple.com, gskachkov at gmail.com,
                    jfbastien at apple.com, keith_miller at apple.com,
                    mark.lam at apple.com, msaboff at apple.com,
                    oliver at apple.com, ticaiolima at gmail.com,
                    utatane.tea at gmail.com

Currently, we just load/store to raw members of the class. We should make it have some public API that take ConcurrentJITLocker as a parameter.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20161111/11af9796/attachment.html>