Page MenuHomePhabricator

[LoopRotate] Don't split loop pass manager

Authored by nikic on Sat, Apr 3, 12:02 PM.



After D99249 we use three different loop pass managers for LICM, LoopRotate and LICM+LoopUnswitch. This happens because LazyBFI and LazyBPI are not preserved by LoopRotate (note that D74640 is no longer needed). Avoid this by marking them as preserved.

My understanding of D86156 is that it is okay to simply preserve them (which LoopUnswitch already does for the same reason) and rely on callbacks to deal with deleted blocks.

Compile-time (only affects LegacyPM):

Diff Detail

Event Timeline

nikic created this revision.Sat, Apr 3, 12:02 PM
nikic requested review of this revision.Sat, Apr 3, 12:02 PM
Herald added a project: Restricted Project. · View Herald TranscriptSat, Apr 3, 12:02 PM
nikic retitled this revision from [LoopRotate] Don't split pass manager to [LoopRotate] Don't split loop pass manager.Sat, Apr 3, 12:04 PM
asbirlea accepted this revision.Mon, Apr 5, 8:58 AM
This revision is now accepted and ready to land.Mon, Apr 5, 8:58 AM
This revision was landed with ongoing or failed builds.Thu, Apr 8, 1:05 PM
This revision was automatically updated to reflect the committed changes.
uabelho added a subscriber: uabelho.Fri, Apr 9, 2:06 AM


Do you know how this change affects the resulting code on average?

I'm seeing a regression in one of our benchmarks, one loop seems to look different after opt and then our backend fails to recognize it as a hardware loop anymore.
I'm not sure if it's possible to make a hardware loop out of this one too, just thought I'd ask if you've seen any major differences in the output?

bjope added a subscriber: bjope.Mon, Apr 12, 5:21 AM