On Mon, 10 Aug 2015, Nathan Sidwell wrote:
> Richard,
>
> This patch fixes the problem I described earlier about min/max generation
> propagating incorrect range information
> (https://gcc.gnu.org/ml/gcc/2015-08/msg00024.html).
>
> I went with creating a new name, if the PHI being modified has m
Richard,
This patch fixes the problem I described earlier about min/max generation
propagating incorrect range information
(https://gcc.gnu.org/ml/gcc/2015-08/msg00024.html).
I went with creating a new name, if the PHI being modified has more than 2
edges. I also modified the testcase that
