On Fri, Oct 11, 2013 at 10:31 PM, Jeff Law wrote:
>
> The problem shown by pr58640 is the more aggressive jump threading is
> recording a jump threading opportunity that crosses through two loop
> headers.
>
> The updating code is not prepared to update the CFG and loop structures in
> that situat
The problem shown by pr58640 is the more aggressive jump threading is
recording a jump threading opportunity that crosses through two loop
headers.
The updating code is not prepared to update the CFG and loop structures
in that situation. The net result is we have two latch edges for a
par
