Reduced the arguments to opt

I assume that a similar fix would then be necessary for loop peeling (and any such loop optimization that clones blocks).

This does not appear to be an issue on the trunk.

Now with transform and test case.

Added test case

After ISEL our compare instructions, multiply, and MAC instructions have real physical register side effects. I'm getting errors from SWP for loops containing these physical register dependencies. Are you aware of this? Is there a way to model physical register dependencies with loop carried dependencies such that we would generate correct code for them?

This version of MachinePipeliner.cpp contains several fixes. Please search for SYNOPSYS for my changes to Brendon's original source.

Very nice work Brandon.

If you have a functional unit that issues in stages such that another instruction of needing the same FU can ussue the very next cycle, then isn't the sum of the cycles too great? Example: