RESOLVED FIXED 200195
[JSC] WeakMapImpl do not need to take cellLock in visitOutputConstraints and main thread
https://bugs.webkit.org/show_bug.cgi?id=200195
Summary [JSC] WeakMapImpl do not need to take cellLock in visitOutputConstraints and ...
Yusuke Suzuki
Reported 2019-07-27 02:40:35 PDT
[JSC] WeakMapImpl do not need to take cellLock in visitOutputConstraint and main thread
Attachments
Patch (4.06 KB, patch)
2019-07-27 02:43 PDT, Yusuke Suzuki
no flags
Patch (4.39 KB, patch)
2022-02-23 17:33 PST, Yusuke Suzuki
no flags
Patch (4.75 KB, patch)
2022-02-23 17:36 PST, Yusuke Suzuki
mark.lam: review+
Yusuke Suzuki
Comment 1 2019-07-27 02:43:22 PDT
Yusuke Suzuki
Comment 2 2022-02-23 17:33:03 PST
Yusuke Suzuki
Comment 3 2022-02-23 17:36:35 PST
Mark Lam
Comment 4 2022-02-23 19:08:08 PST
Comment on attachment 453060 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=453060&action=review r=me > Source/JavaScriptCore/ChangeLog:8 > + WeakMapImpl::visitOutputConstraints is called in the constraint solver, and it does not modify the buffer of WeakMapImpl. Can you remove this part: "and it does not modify the buffer of WeakMapImpl"? It is not relevant, correct? The only relevant detail is what you stated below i.e. the constraint solver runs and rehash can never be run concurrently. Also, if concurrency were an issue, m_buffer isn't the only thing that needs to be protected: m_capacity does too. So, it seems strange to draw attention to the buffer here.
Yusuke Suzuki
Comment 5 2022-02-23 20:23:04 PST
Comment on attachment 453060 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=453060&action=review >> Source/JavaScriptCore/ChangeLog:8 >> + WeakMapImpl::visitOutputConstraints is called in the constraint solver, and it does not modify the buffer of WeakMapImpl. > > Can you remove this part: "and it does not modify the buffer of WeakMapImpl"? It is not relevant, correct? The only relevant detail is what you stated below i.e. the constraint solver runs and rehash can never be run concurrently. > > Also, if concurrency were an issue, m_buffer isn't the only thing that needs to be protected: m_capacity does too. So, it seems strange to draw attention to the buffer here. OK, dropped.
Yusuke Suzuki
Comment 6 2022-02-24 00:57:20 PST
Radar WebKit Bug Importer
Comment 7 2022-02-24 00:58:20 PST
Note You need to log in before you can comment on or make changes to this bug.