Closed
Bug 845573
Opened 11 years ago
Closed 11 years ago
GC: allocate singleton frontend objects from tenured
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla22
People
(Reporter: terrence, Unassigned)
References
Details
Attachments
(1 file)
3.76 KB,
patch
|
bhackett1024
:
review+
|
Details | Diff | Splinter Review |
In particular this immediately tenures the self-hosting global, with its hundreds of slots.
Attachment #718710 -
Flags: review?(bhackett1024)
Comment 1•11 years ago
|
||
Comment on attachment 718710 [details] [diff] [review] v0 Review of attachment 718710 [details] [diff] [review]: ----------------------------------------------------------------- ::: js/src/frontend/BytecodeEmitter.cpp @@ +3483,5 @@ > static bool > EmitSingletonInitialiser(JSContext *cx, BytecodeEmitter *bce, ParseNode *pn) > { > RootedValue value(cx); > + if (!pn->getConstantValue(cx, bce->sc->needStrictChecks(), &value, MaybeSingletonObject)) This is the only use of getConstantValue, so you can lose the newKind argument and just always allocate initializer objects from the tenured heap.
Attachment #718710 -
Flags: review?(bhackett1024) → review+
Reporter | ||
Comment 2•11 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/5a0004e62900
Comment 3•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/5a0004e62900
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla22
You need to log in
before you can comment on or make changes to this bug.
Description
•