Closed Bug 578820 Opened 14 years ago Closed 13 years ago

JM: Limit study to determine performance impact of type guards

Categories

(Core :: JavaScript Engine, enhancement)

Product:
Core
Component:
JavaScript Engine
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

()

Status:
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.
Blocks: JaegerSpeed
Cool idea, related to bug 557407 I think. Cc'ing usual suspects.

/be
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.
Rendered irrelevant by IonMonkey and extensive type inference work, closing to avoid clutter.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.