These instructions have 3 operands that can be commuted. The first commute we find may not be the best. So we should keep searching even after we perform a commute.
Details
Details
Diff Detail
Diff Detail
- Repository
- rL LLVM
Event Timeline
Comment Actions
Don't continue search if we found a non-aggressive commute. We don't want an aggressive commute to overwrite it.
Comment Actions
Hi Craig,
This change-set looks good to me.
-Vyacheslav
lib/CodeGen/TwoAddressInstructionPass.cpp | ||
---|---|---|
1386 ↗ | (On Diff #137831) | I was looking for some potential problems on the caller side of the routine you changed; have not found anything interesting/wrong there, but noticed this odd line. |