Patch coming. Details will in the ChangeLog in the patch.
Created attachment 223522 [details] the patch.
Comment on attachment 223522 [details] the patch. We don't need a special case for dropAllLocks() now that we're on the C stack. You might be able to just make dropAllLocksUnconditionally be the only dropAllLocks.
Comment on attachment 223522 [details] the patch. View in context: https://bugs.webkit.org/attachment.cgi?id=223522&action=review > Source/JavaScriptCore/ChangeLog:12 > + In the process of switching to iOS implementation, I compared the typo: to "the" iOS implementation. Will fix. > Source/JavaScriptCore/ChangeLog:14 > + implementation has a bug in dropAllLocks() and dropAllLocksUnconditionally().(). Redundant "().". Will fix.
Comment on attachment 223522 [details] the patch. View in context: https://bugs.webkit.org/attachment.cgi?id=223522&action=review > Source/JavaScriptCore/ChangeLog:16 > + The bug is that they do not clear our m_vm->stackPointerAtVMEntry and typo: our ==> out. > Source/JavaScriptCore/ChangeLog:18 > + JSLock::unlock() to dropAllLocks() and dropAllLocksUnconditionally(). Missing ")" after "JSLock::unlock()". Will fix.
Comment on attachment 223522 [details] the patch. Split out the bug fix, please.
Created attachment 223534 [details] patch 2: just there part that makes everyone do drop/grab locks the iOS way.
Comment on attachment 223534 [details] patch 2: just there part that makes everyone do drop/grab locks the iOS way. r=me
Thanks. Landed in r163685: <http://trac.webkit.org/r163685>.