http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58640
--- Comment #4 from Jeffrey A. Law <law at redhat dot com> --- We're ending up with latches from two different loops going to the same destination due to the jump thread path passing through multiple loops. This ultimately causes the unroller to go nuts. This should be fairly easy to catch & avoid. And this brings to the forefront a question that's been slowly building in the back of my mind. Specifically, given a jump threading path, we have the ability now to lop off the tail of the path if threading all the way to the tail would ultimately force cancellation of the jump thread request. Lopping off the tail may result in better code than totally cancelling the request. This testcase is a good example. Anyway, I'll be pondering how we want to deal with that as well.
