Closed
Bug 908294
Opened 11 years ago
Closed 11 years ago
More fixes for ExclusiveContext zones with TI enabled
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
mozilla26
People
(Reporter: bhackett1024, Unassigned)
References
Details
Attachments
(1 file)
6.31 KB,
patch
|
billm
:
review+
|
Details | Diff | Splinter Review |
Bug 906060 missed some spots here. This also fixes a place where lazy parsing was needlessly disabled when parsing scripts off thread.
Attachment #794141 -
Flags: review?(wmccloskey)
Comment on attachment 794141 [details] [diff] [review]
patch
Review of attachment 794141 [details] [diff] [review]:
-----------------------------------------------------------------
::: js/src/jscntxt.h
@@ +263,5 @@
> JSAtomState &names() { return runtime_->atomState; }
> StaticStrings &staticStrings() { return runtime_->staticStrings; }
> PropertyName *emptyString() { return runtime_->emptyString; }
> FreeOp *defaultFreeOp() { return runtime_->defaultFreeOp(); }
> + bool useHelperThreads() { return runtime_->useHelperThreads(); }
This is unused, but maybe you want it for later?
::: js/src/jsinfer.cpp
@@ +6129,5 @@
>
> TypeObject *
> +ExclusiveContext::getLazyType(Class *clasp, TaggedProto proto)
> +{
> + JS_ASSERT_IF(proto.isObject(), compartment() == proto.toObject()->compartment());
Can you assert that we're not in the atoms compartment? Or, if we are, that we have a JSContext.
Attachment #794141 -
Flags: review?(wmccloskey) → review+
Reporter | ||
Comment 2•11 years ago
|
||
Comment 3•11 years ago
|
||
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla26
You need to log in
before you can comment on or make changes to this bug.
Description
•