Closed
Bug 1066197
Opened 10 years ago
Closed 10 years ago
Some iterator cleanup
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla35
People
(Reporter: jandem, Assigned: jandem)
References
Details
Attachments
(4 files)
12.82 KB,
patch
|
bhackett1024
:
review+
|
Details | Diff | Splinter Review |
3.44 KB,
patch
|
bhackett1024
:
review+
|
Details | Diff | Splinter Review |
16.03 KB,
patch
|
bhackett1024
:
review+
|
Details | Diff | Splinter Review |
10.34 KB,
patch
|
bhackett1024
:
review+
|
Details | Diff | Splinter Review |
There's some cruft here, like js_IteratorMore taking a MutableHandleValue where it just wants a bool* and we can also remove jit::IteratorMore and js;:IteratorMore.
Assignee | ||
Comment 1•10 years ago
|
||
Will post another patch to rename it to js::IteratorMore.
Attachment #8488076 -
Flags: review?(bhackett1024)
Updated•10 years ago
|
Attachment #8488076 -
Flags: review?(bhackett1024) → review+
Assignee | ||
Comment 2•10 years ago
|
||
Part 1: https://hg.mozilla.org/integration/mozilla-inbound/rev/8a45ca4767de
Keywords: leave-open
Assignee | ||
Comment 3•10 years ago
|
||
js::IteratorNext has a path for native iterators and then calls js_IteratorNext. js_IteratorNext does exactly the same thing, so let's just use that one everywhere.
Attachment #8488678 -
Flags: review?(bhackett1024)
Updated•10 years ago
|
Attachment #8488678 -
Flags: review?(bhackett1024) → review+
Assignee | ||
Comment 4•10 years ago
|
||
Move js_IteratorMore, js_IteratorNext, js_Suppress* and js_ThrowStopIteration into the js namespace and drop the js_*.
Attachment #8488679 -
Flags: review?(bhackett1024)
Updated•10 years ago
|
Attachment #8488679 -
Flags: review?(bhackett1024) → review+
Assignee | ||
Comment 5•10 years ago
|
||
I want to get rid of iterValue, but having it in the runtime simplifies some other patches before we are there.
Attachment #8488725 -
Flags: review?(bhackett1024)
Comment 6•10 years ago
|
||
Comment on attachment 8488725 [details] [diff] [review] Part 4 - Move iterValue from JSContext to JSRuntime Review of attachment 8488725 [details] [diff] [review]: ----------------------------------------------------------------- ::: js/src/jsiter.cpp @@ +1019,5 @@ > /* > * Make sure the more/next state machine doesn't get stuck. A value might > * be left in iterValue when a trace is left due to an interrupt after > * JSOP_MOREITER but before the value is picked up by FOR*. > */ Wow, this comment is an antique.
Attachment #8488725 -
Flags: review?(bhackett1024) → review+
Comment 7•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/8a45ca4767de
Assignee | ||
Comment 8•10 years ago
|
||
Parts 2 and 3: https://hg.mozilla.org/integration/mozilla-inbound/rev/5d9353b3572c https://hg.mozilla.org/integration/mozilla-inbound/rev/7e47a9f5e048 Dropping part 4, bug 831585 removes cx->iterValue and moving it first is not necessary after all.
Keywords: leave-open
https://hg.mozilla.org/mozilla-central/rev/5d9353b3572c https://hg.mozilla.org/mozilla-central/rev/7e47a9f5e048
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla35
Updated•10 years ago
|
Flags: qe-verify-
You need to log in
before you can comment on or make changes to this bug.
Description
•