To avoid unnecessary frame state information dropping across back edges we may be able to unroll low trip-count loops in the font end. Branchy or call-oriented code will have less benefit since it has to drop frame state info above branch targets and sync before a call (respectively), so maybe there's an easy heuristic we can flag on conditionals/invocations in the AST. The induction variable has to be effectively scoped to the loop body and, to make it easy, require all defs to be scoped to the loop header.
Is this still relevant? Certainly doesn't sounds like it's JM-specific, but it might have been obsoleted by other changes in the meantime.
I don't think this has been relevant since before JM+TI came around, as JM+TI could carry registers across loop backdges.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.