[Webkit-unassigned] [Bug 202392] New: [JSC] Thread JSGlobalObject* instead of ExecState*

[bugzilla-daemon at webkit.org]

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

            Bug ID: 202392
           Summary: [JSC] Thread JSGlobalObject* instead of ExecState*
           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: ysuzuki at apple.com

But, it is super costly if we ends up calling lexicalGlobalObject().
So, we need to put JSGlobalObject* in JSFunction/InternalFunction. And trampoline for them will get objects and pass them to the host-function.
Then, the host-function signature is changed to `hostFunction(CallFrame*, JSGlobalObject*)`. CallFrame* is necessary since we still need to access thisValue, arguments etc. residing on the stack.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20191001/073f4d27/attachment-0001.html>