RESOLVED INVALID 142071
BytecodeGenerator::constLocal() behaves identically to BytecodeGenerator::local() for the purposes of its one caller
https://bugs.webkit.org/show_bug.cgi?id=142071
Summary BytecodeGenerator::constLocal() behaves identically to BytecodeGenerator::loc...
Filip Pizlo
Reported 2015-02-26 19:16:40 PST
So, remove constLocal(). The behavioral differences are: - constLocal() doesn't have a special case for "this" that overrides other checks like the shouldOptimizeLocals() check. But the one user of constLocal() is for the "const x" expression, and "const this" doesn't parse. - constLocal() won't createArgumentsIfNecessary() for "arguments". But it's harmless if it does, since its one user assigns to the local. So, we can remove constLocal() and make its one caller use local() instead.
Attachments
the patch (3.80 KB, patch)
2015-02-26 19:17 PST, Filip Pizlo
mark.lam: review+
the patch (4.76 KB, patch)
2015-02-26 19:41 PST, Filip Pizlo
benjamin: review+
Filip Pizlo
Comment 1 2015-02-26 19:17:43 PST
Created attachment 247483 [details] the patch
Mark Lam
Comment 2 2015-02-26 19:39:09 PST
Comment on attachment 247483 [details] the patch View in context: https://bugs.webkit.org/attachment.cgi?id=247483&action=review Missing ChangeLog. The text in your bugzilla description is good to have in the ChangeLog. r=me with ChangeLog added. > Source/JavaScriptCore/bytecompiler/NodesCodegen.cpp:4 > +* Copyright (C) 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2012, 2013, 2015 Apple Inc. All rights reserved. nit: You can collapse this to: * Copyright (C) 2003-2009, 2012-2013, 2015 Apple Inc. All rights reserved.
Filip Pizlo
Comment 3 2015-02-26 19:41:54 PST
Created attachment 247484 [details] the patch And now, with a ChangeLog!
Filip Pizlo
Comment 4 2015-02-26 21:13:20 PST
Alexey Proskuryakov
Comment 5 2015-02-26 22:09:39 PST
This broke Windows tests: ** The following JSC stress test failures have been introduced: stress/const-arguments.js.always-trigger-copy-phase stress/const-arguments.js.default stress/const-arguments.js.dfg-eager stress/const-arguments.js.dfg-eager-no-cjit-validate stress/const-arguments.js.no-cjit-validate-phases stress/const-arguments.js.no-llint
Filip Pizlo
Comment 6 2015-02-26 23:12:16 PST
(In reply to comment #5) > This broke Windows tests: > > ** The following JSC stress test failures have been introduced: > stress/const-arguments.js.always-trigger-copy-phase > stress/const-arguments.js.default > stress/const-arguments.js.dfg-eager > stress/const-arguments.js.dfg-eager-no-cjit-validate > stress/const-arguments.js.no-cjit-validate-phases > stress/const-arguments.js.no-llint It might have broken other things too. I'm looking.
Brent Fulgham
Comment 7 2015-02-26 23:19:08 PST
This broke the iOS build and Windows debug tests. This should be rolled out if it cannot be fixed ASAP.
Filip Pizlo
Comment 8 2015-02-26 23:23:26 PST
(In reply to comment #7) > This broke the iOS build and Windows debug tests. > > This should be rolled out if it cannot be fixed ASAP. I'm also seeing lots of breakage. I agree with rollout.
Filip Pizlo
Comment 9 2015-02-26 23:27:02 PST
Filip Pizlo
Comment 10 2015-02-27 07:33:13 PST
It looks like there is some bizarre behavior here. I'll have to address it a different way in my refactoring in bug 141174.
Note You need to log in before you can comment on or make changes to this bug.