Lines Matching full:phis
73 // because it would increase the number of PHIs entering the block,
75 // bad when the PHIs are in the header of a loop.
100 // Add all operands to the new PHIs.
143 // especially bad when the PHIs are in the header of a loop.
169 // if one of the PHIs has a constant for the index. The index may be
181 // also requires a PHI, we'd be introducing more PHIs than we're
220 // Add all operands to the new PHIs.
410 // Be careful about transforming integer PHIs. We don't want to pessimize
616 /// inttoptr. We should produce new PHIs in the right type.
620 // of PHIs, along with their offset. These are the things we want to rewrite.
623 // PHIs are often mutually cyclic, so we keep track of a whole set of PHI
625 // revisiting PHIs, PHIsInspected is a ordered list of PHIs that we need to
683 // If this phi node is transformable, create new PHIs for all the pieces
697 // introduce redundant PHIs.
737 // If the incoming value was a PHI, and if it was one of the PHIs we
756 // If the incoming value was a PHI, and if it was one of the PHIs we are
800 // FIXME: The hasOneUse check will fail for PHIs that use the value more
848 // there is no need to recursively scan other phis.
866 // If there are multiple PHIs, sort their operands so that they all list
867 // the blocks in the same order. This will help identical PHIs be eliminated
