Closed
Bug 922168
Opened 11 years ago
Closed 11 years ago
Don't use JSContext in UseNewTypeForInitializer
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
mozilla27
People
(Reporter: bhackett1024, Assigned: bhackett1024)
References
Details
Attachments
(1 file)
|
12.47 KB,
patch
|
jandem
:
review+
|
Details | Diff | Splinter Review |
This function takes a JSContext and is used in IonBuilder. The context is only used for checking if TI is enabled, though, and since attempts to give a singleton type to objects are ignored when TI is disabled, I don't think this check is helping anything.
Attachment #812093 -
Flags: review?(jdemooij)
|
||
Updated•11 years ago
|
Attachment #812093 -
Flags: review?(jdemooij) → review+
|
Assignee | |
Comment 1•11 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/0ede95a5c915
|
||
Comment 2•11 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/0ede95a5c915
Assignee: nobody → bhackett1024
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla27
You need to log in
before you can comment on or make changes to this bug.
Description
•