JM: Limit study to determine performance impact of type guards

RESOLVED WONTFIX

Status

()

Core
JavaScript Engine
--
enhancement
RESOLVED WONTFIX
8 years ago
7 years ago

People

(Reporter: adrake, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

8 years ago
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

8 years ago
Blocks: 578133
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.
(Reporter)

Comment 3

7 years ago
Rendered irrelevant by IonMonkey and extensive type inference work, closing to avoid clutter.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.