RESOLVED FIXED 80924
[V8][Refactoring] Remove getCachedWrapperSlow() from V8Bindings.cpp
https://bugs.webkit.org/show_bug.cgi?id=80924
Summary [V8][Refactoring] Remove getCachedWrapperSlow() from V8Bindings.cpp
Kentaro Hara
Reported 2012-03-12 18:46:43 PDT
getCachedWrapperSlow() is called by getCachedWrapper() only, and getCachedWrapperSlow() just calls getCachedWrapperInline(). Thus, we can expand getCachedWrapperInline() into getCachedWrapper(), which removes getCachedWrapperSlow().
Attachments
Patch (4.64 KB, patch)
2012-03-12 18:49 PDT, Kentaro Hara
no flags
Kentaro Hara
Comment 1 2012-03-12 18:49:05 PDT
Adam Barth
Comment 2 2012-03-12 19:09:44 PDT
Comment on attachment 131487 [details] Patch This doesn't slow things down by inlining too much code?
Kentaro Hara
Comment 3 2012-03-12 19:14:48 PDT
(In reply to comment #2) > (From update of attachment 131487 [details]) > This doesn't slow things down by inlining too much code? I confirmed no perf regression in DOM core tests of DROMAEO. I do not think this change increases the inlined code. This change just moves getCachedWrapperInline(), which had been already inlined.
Adam Barth
Comment 4 2012-03-12 19:17:12 PDT
Comment on attachment 131487 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=131487&action=review > Source/WebCore/bindings/v8/V8DOMWrapper.h:-135 > - return getCachedWrapperSlow(node); This function used to be out-of-line, but I think that's fine.
Kentaro Hara
Comment 5 2012-03-12 19:18:10 PDT
(In reply to comment #4) > > Source/WebCore/bindings/v8/V8DOMWrapper.h:-135 > > - return getCachedWrapperSlow(node); > > This function used to be out-of-line, but I think that's fine. Ah, I got it. Thanks for the clarification. Let me land it.
WebKit Review Bot
Comment 6 2012-03-12 21:22:22 PDT
Comment on attachment 131487 [details] Patch Clearing flags on attachment: 131487 Committed r110536: <http://trac.webkit.org/changeset/110536>
WebKit Review Bot
Comment 7 2012-03-12 21:22:26 PDT
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.