Open Bug 1959078 Opened 1 year ago Updated 1 year ago

Run loop unrolling before GVN, rather than rerunning GVN after it

Categories

(Core :: JavaScript: WebAssembly, enhancement, P3)

enhancement

Tracking

()

People

(Reporter: jseward, Unassigned)

References

(Blocks 1 open bug)

Details

The MIR loop unroller in bug 1950284 runs fairly late in the MIR transformation
pipe (for wasm, at least), and long after GVN. If any loops in a function do
get unrolled and/or peeled, then we try to take advantage of any optimisation
opportunities thereby exposed by rerunning GVN and possibly FoldEmptyBlocks
and BuildDominatorTree.

Such post-hoc opportunistic tidying is expensive. It might be cheaper to
perform unrolling before the main GVN pass instead, instead of re-running
GVN afterwards.

Severity: -- → N/A
You need to log in before you can comment on or make changes to this bug.