Closed
Bug 578820
Opened 14 years ago
Closed 14 years ago
JM: Limit study to determine performance impact of type guards
Categories
(Core :: JavaScript Engine, enhancement)
Core
JavaScript Engine
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: adrake, Unassigned)
References
Details
Use some form of oracle to eliminate all type guards in, e.g., SunSpider, and determine the performance gained by doing so. This would let us put an upper bound on wins by this mechanism.
Reporter | ||
Updated•14 years ago
|
Blocks: JaegerSpeed
Comment 1•14 years ago
|
||
Cool idea, related to bug 557407 I think. Cc'ing usual suspects.
/be
Comment 2•14 years ago
|
||
Note that type inference does better than just eliminating type guards -- code normally generated in the OOL path can be inlined, eliminating branches and greatly benefiting cache locality.
Reporter | ||
Comment 3•14 years ago
|
||
Rendered irrelevant by IonMonkey and extensive type inference work, closing to avoid clutter.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•