Closed
Bug 1500836
Opened 6 years ago
Closed 5 years ago
[BinAST] delete operator on an argument cannot find binding
Categories
(Core :: JavaScript Engine, defect, P3)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla66
People
(Reporter: arai, Assigned: arai)
References
Details
Attachments
(2 files)
553 bytes,
application/octet-stream
|
Details | |
2.12 KB,
patch
|
Yoric
:
review+
|
Details | Diff | Splinter Review |
encoded from https://searchfox.org/mozilla-central/source/js/src/jit-test/tests/parser/bug-888002-2.js tested on m-i 716178d41d26 Configure flags: --enable-warnings-as-errors --disable-optimize --enable-debug Runtime flag: -B del-arg.binjs Actual result: Error: Assertion failed: got true, expected false the problematic part is (function (x) { ... assertEq(delete x, false); }()); that `delete x` fails because it cannot find the binding name in js::DeleteNameOperation
Assignee | ||
Comment 1•6 years ago
|
||
Assignee | ||
Comment 2•6 years ago
|
||
delete with name operand should call setBindingsAccessedDynamically
Assignee: nobody → arai.unmht
Status: NEW → ASSIGNED
Assignee | ||
Comment 3•6 years ago
|
||
in order to throw the same error as regular parser on "delete name" in strict mode, depends bug 1502280.
Depends on: 1502280
Assignee | ||
Comment 4•6 years ago
|
||
based on bug 1502792 patch.
Attachment #9023160 -
Flags: review?(dteller)
Comment on attachment 9023160 [details] [diff] [review] Call setBindingsAccessedDynamically if delete with name operand appears in BinAST. Review of attachment 9023160 [details] [diff] [review]: ----------------------------------------------------------------- Ouch, I had entirely forgotten that we can do that. JS has a few scary corners :)
Attachment #9023160 -
Flags: review?(dteller) → review+
Assignee | ||
Comment 6•5 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/a9f1fba8641a368ffdbea3b7daf62c3a1a6a4152 Bug 1500836 - Call setBindingsAccessedDynamically if delete with name operand appears in BinAST. r=Yoric
Comment 7•5 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox66:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla66
Updated•5 years ago
|
status-firefox65:
--- → ?
You need to log in
before you can comment on or make changes to this bug.
Description
•