Open gbossu opened 1 week ago
Hi @gbossu, as we did before, we could integrate the 1st and 3rd commits before, as they are standalone changes.
Hi @gbossu, as we did before, we could integrate the 1st and 3rd commits before, as they are standalone changes.
I'm actually tempted to drop the 3rd commit and do not have AIEMaxLatencyFinder/RegionEndEdges care about "timed"/"fixed" instructions. I think it makes sense if they keep focusing on successor MBBs instead. For dependencies between "fixed" and "free" instructions, I can add them in the EmitFixedSUnits
mutator instead. Any opinion?
Hi @gbossu, as we did before, we could integrate the 1st and 3rd commits before, as they are standalone changes.
I'm actually tempted to drop the 3rd commit and do not have AIEMaxLatencyFinder/RegionEndEdges care about "timed"/"fixed" instructions. I think it makes sense if they keep focusing on successor MBBs instead. For dependencies between "fixed" and "free" instructions, I can add them in the
EmitFixedSUnits
mutator instead. Any opinion?
Is this case, I think it makes sense, as we are introducing this new mutator! In this way we can also restrict a bit more the changes.
Any more comments @andcarminati @martien-de-jong ?
Hi @gbossu, I finished my review and left few suggestions. Nice piece of engineering that will make a lot more difference for the post-swp as we increase its use.
Better review commit by commit, a lot of them are NFC and prepare for the final commit which enables interleaving.
QoR shows only improvements. Those will get bigger as we increase the scope of the post-pipeliner.