[PATCH] Prevent ifcvt from moving computations into loop

[Zdenek Dvorak]

Hello,

> > are you sure?
> 
> No, but..
> 
> > I don't know for sure, but updating it in ifcvt seems quite painful
> 
> .. we shouldn't *need* any updating, because we're going to
> explicitly *prevent* moving across loop level boundaries.
> 
> That is the whole point of the excersise, isn't it?

sounds reasonable (not that I would be able to verify that really none
of the transformations in ifcvt may not make something unexpected with
it, but it should not cause much problems anyway).  What remains is
whether noone will object against building and throwing away the loops
structure three more times per compilation?

Zdenek