On 04/02/2012 08:42 AM, Richard Guenther wrote:
On Mon, 2 Apr 2012, Richard Guenther wrote:
After going through a gazillion of candidate fixes for PR52756, a
case where jump threading destroys loops in a non-recoverable way,
I settled with the following. The issue is that we thread both
the l
On Mon, 2 Apr 2012, H.J. Lu wrote:
> On Mon, Apr 2, 2012 at 5:32 AM, Richard Guenther wrote:
> >
> > After going through a gazillion of candidate fixes for PR52756, a
> > case where jump threading destroys loops in a non-recoverable way,
> > I settled with the following. The issue is that we thr
On Mon, Apr 2, 2012 at 5:32 AM, Richard Guenther wrote:
>
> After going through a gazillion of candidate fixes for PR52756, a
> case where jump threading destroys loops in a non-recoverable way,
> I settled with the following. The issue is that we thread both
> the loop latch and the loop entry e
On Mon, 2 Apr 2012, Richard Guenther wrote:
>
> After going through a gazillion of candidate fixes for PR52756, a
> case where jump threading destroys loops in a non-recoverable way,
> I settled with the following. The issue is that we thread both
> the loop latch and the loop entry edge but the
After going through a gazillion of candidate fixes for PR52756, a
case where jump threading destroys loops in a non-recoverable way,
I settled with the following. The issue is that we thread both
the loop latch and the loop entry edge but the code is not prepared
for that. Another possible fix w
