IonMonkey: rerun GVN after LICM (or subset)

NEW
Unassigned

Status

()

Core
JavaScript Engine
5 years ago
4 years ago

People

(Reporter: h4writer, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
This is visible in raytrace.js:709 with almost all functions inlined. 

LICM hoists a lot of definitions out of the loop. Afterwards there are some definitions that could get removed again by running GVN again.
Off-course we could be smarter and only check hoisted MIR's and we only have to compare in the current block. So could be a really small pass.

Shows a 1.5% improvement on raytrace by running full GVN again after LICM
(Reporter)

Updated

5 years ago
Blocks: 768745

Updated

4 years ago
Duplicate of this bug: 1009304
(Assignee)

Updated

4 years ago
Assignee: general → nobody
You need to log in before you can comment on or make changes to this bug.