Actions
Bug #3192
closed
mdb save-args matching should accept more agressive insn scheduling
Start date:
2012-09-14
Due date:
% Done:
100%
Estimated time:
Difficulty:
Medium
Tags:
Gerrit CR:
Description
While the save-args matching accepts that the actual argument saving prologue may be interleaved with other unrelated instructions by the insn scheduler, it does not expect that this may be true of actually saving the frame pointer and establishing the frame.
It really needs to allow for this too, as insns unrelated to the frame may unfortunately get scheduled before, or amongst, the classic prologue by optimization.
We should also increase the maximum distance into the function we're willing to scan.
Updated by Rich Lowe almost 9 years ago
- Status changed from In Progress to Resolved
- % Done changed from 80 to 100
Resolved in 2d4be7a
Actions