RESOLVED FIXED 129170
Add extra space to op_call and related opcodes
https://bugs.webkit.org/show_bug.cgi?id=129170
Summary Add extra space to op_call and related opcodes
Oliver Hunt
Reported 2014-02-21 14:23:16 PST
Add extra space to op_call and related opcodes
Attachments
Patch (10.31 KB, patch)
2014-02-21 14:25 PST, Oliver Hunt
mark.lam: review+
Oliver Hunt
Comment 1 2014-02-21 14:25:16 PST
Mark Lam
Comment 2 2014-02-21 14:28:26 PST
Comment on attachment 224908 [details] Patch r=me
Daniel Bates
Comment 3 2014-02-21 14:29:31 PST
Comment on attachment 224908 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=224908&action=review > Source/JavaScriptCore/ChangeLog:9 > + slot to the op_call instructions, and refactoring to make simlar Nit: simlar => similar
Daniel Bates
Comment 4 2014-02-21 14:30:06 PST
Comment on attachment 224908 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=224908&action=review > Source/JavaScriptCore/ChangeLog:10 > + changes easier in future. Nit: "in future" => "in the future"
Oliver Hunt
Comment 5 2014-02-21 14:32:19 PST
Filip Pizlo
Comment 6 2014-02-21 18:12:16 PST
Why? Did you test performance? Inlining is based on bytecode size, and you just made everything larger.
Oliver Hunt
Comment 7 2014-02-21 20:26:11 PST
(In reply to comment #6) > Why? > > Did you test performance? Inlining is based on bytecode size, and you just made everything larger. Because call_var_args needs an extra argument, i didn't think about the performance impact because i forgot that inlining was based on # of operands rather than # of opcodes. I'll see if i can fix this, or alternatively just remove the requirement that call_var_args be the same size as all the other calls.
Filip Pizlo
Comment 8 2014-02-21 21:12:09 PST
(In reply to comment #7) > (In reply to comment #6) > > Why? > > > > Did you test performance? Inlining is based on bytecode size, and you just made everything larger. > > Because call_var_args needs an extra argument, i didn't think about the performance impact because i forgot that inlining was based on # of operands rather than # of opcodes. > > I'll see if i can fix this, or alternatively just remove the requirement that call_var_args be the same size as all the other calls. I think it's enough to just measure it and make sure that nothing broke
Oliver Hunt
Comment 9 2014-02-21 21:38:59 PST
(In reply to comment #8) > (In reply to comment #7) > > (In reply to comment #6) > > > Why? > > > > > > Did you test performance? Inlining is based on bytecode size, and you just made everything larger. > > > > Because call_var_args needs an extra argument, i didn't think about the performance impact because i forgot that inlining was based on # of operands rather than # of opcodes. > > > > I'll see if i can fix this, or alternatively just remove the requirement that call_var_args be the same size as all the other calls. > > I think it's enough to just measure it and make sure that nothing broke kk
Oliver Hunt
Comment 10 2014-02-22 13:26:39 PST
(In reply to comment #8) > (In reply to comment #7) > > (In reply to comment #6) > > > Why? > > > > > > Did you test performance? Inlining is based on bytecode size, and you just made everything larger. > > > > Because call_var_args needs an extra argument, i didn't think about the performance impact because i forgot that inlining was based on # of operands rather than # of opcodes. > > > > I'll see if i can fix this, or alternatively just remove the requirement that call_var_args be the same size as all the other calls. > > I think it's enough to just measure it and make sure that nothing broke I don't see a regression under jsc on my MBP. Just about to run the DRT hosted version.
Note You need to log in before you can comment on or make changes to this bug.