Closed
Bug 1008138
Opened 12 years ago
Closed 5 years ago
IonMonkey: remove pushTypeBarrier out of pushDOMTypeBarrier
Categories
(Core :: JavaScript Engine: JIT, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: h4writer, Unassigned)
References
Details
Currently we emit a regular type barrier when the typeset doesn't match the native JITInfo information. This is actually not needed anymore. In most cases we can just take the type information provided by JITInfo and just be done with it.
1) We can decide to not use pushTypeBarrier, except for MIRType_Object. We do want to bailout and record better information than JITInfo can provide for this.
2) Use MFilterTypeSet to have runtime checks in debug builds that the JITInfo given by a target is indeed correct! (depends on 1008111)
Comment 1•5 years ago
|
||
No longer valid with Warp.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•