RESOLVED FIXED Bug 65883
DFG JIT has no way of propagating predictions to loads and calls
https://bugs.webkit.org/show_bug.cgi?id=65883
Summary DFG JIT has no way of propagating predictions to loads and calls
Filip Pizlo
Reported 2011-08-08 15:38:49 PDT
The DFG JIT sometimes wants to predict the type of a variable based on how it gets used. But it can only do this if the variable was assigned to by loading from the register file or from global variables. It should be able to also do this if the variable is the result of a heap load (GetById, GetByVal) or a call.
Attachments
the patch (11.11 KB, patch)
2011-08-08 15:56 PDT, Filip Pizlo
barraclough: review+
barraclough: commit-queue-
the patch (fix for review) (11.11 KB, patch)
2011-08-09 17:15 PDT, Filip Pizlo
no flags
Filip Pizlo
Comment 1 2011-08-08 15:56:04 PDT
Created attachment 103306 [details] the patch
Filip Pizlo
Comment 2 2011-08-08 16:47:09 PDT
Comment on attachment 103306 [details] the patch All tests pass.
Gavin Barraclough
Comment 3 2011-08-09 16:48:05 PDT
Comment on attachment 103306 [details] the patch View in context: https://bugs.webkit.org/attachment.cgi?id=103306&action=review Sorry to cq- for a typo, but I think there is a grammar error in the change log. :-) Otherwise all looks good. I think we might want a prediction for more (all) node types in the future, so may want to break this out as a separate field, but reuse of opInfo2 seems like a good call, at least for now. > Source/JavaScriptCore/ChangeLog:8 > + This introduces the capability to stored predictions on graph stored -> store ?
Filip Pizlo
Comment 4 2011-08-09 17:15:38 PDT
Created attachment 103423 [details] the patch (fix for review)
WebKit Review Bot
Comment 5 2011-08-09 17:51:25 PDT
Comment on attachment 103423 [details] the patch (fix for review) Clearing flags on attachment: 103423 Committed r92734: <http://trac.webkit.org/changeset/92734>
WebKit Review Bot
Comment 6 2011-08-09 17:51:30 PDT
All reviewed patches have been landed. Closing bug.
Filip Pizlo
Comment 7 2011-08-09 19:04:17 PDT
When combined with https://bugs.webkit.org/show_bug.cgi?id=65949, this produces a 20% slow-down in v8-crypto without any significant speed-ups anywhere. It should probably be disabled.
Note You need to log in before you can comment on or make changes to this bug.