JIT optimization: tail merge #8795
Description
Tracking issue for a classic codesize optimization that's not currently implemented in RyuJIT. The optimization would find predecessors of a common successor (along non-critical edges) that all end in equivalent sequences leading up to the join, and move the gotos and join earlier such that statically only one copy of the equivalent sequence remains. We'd want to treat returns as "joining" at the continuation so that we could eliminate redundant epilogs when a function has (statically) multiple returns of the same expression.
category:cq
theme:optimization
skill-level:expert
cost:medium