Reorder VPlan transforms slightly so they are all grouped together,
after disabling Value -> VPValue lookup. In terms of codegen impact,
this should be NFC modulo a small number of instruction reorderings.
Preparation to split up tryToBuildVPlanWithVPRecipes in a follow-up.
(Possible follow-up:) Could adjustRecipesForReductions() be refactored to walk the def-use chains of recipes rather than rely on retrieving recipes of recorded Instructions, so it could (continue to) be next to adjust[RecipesFor]FixedOrderRecurrences()? The latter part of adjustRecipesForReductions() which introduces selects in case of fold-tail is already Value2VPValue-free.
The call to RecipeBuilder.fixHeaderPhis() should indeed be part of the initial VPlan construction as it completes the def-use relations of reduction and FOR header phi's, using Value2VPValue. Still, it too could walk header phi recipes instead of relying on the recorded PhisToFix?