[Webkit-unassigned] [Bug 168977] New: Remove setExclusiveThread() and peers from the JSLock.

[bugzilla-daemon at webkit.org]

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

            Bug ID: 168977
           Summary: Remove setExclusiveThread() and peers from the JSLock.
    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: mark.lam at apple.com

JSLock::setExclusiveThread() was only used by WebCore.  Benchmarking with Speedometer, we see that removal of exclusive thread status has no measurable impact on performance.  So, let's remove the code for handling exclusive thread status, and simplify the JSLock code.

-- 
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/20170228/4a0189a9/attachment.html>