Hi,
I believe this tests has been wrongly modified previously.  It is to test that the exit check on
pointer shouldn't be replaced by integer IV.  Somehow GCC starts replacing the check on
integer IV with pointer IV.  It's valid, though inefficient.  And somehow we starting checking
this iv replacement.   This patch rectifies it by specifically checking the check on pointer
shouldn't be replaced.  

Bootstrap and test in series on x86_64.  Is it OK?
Thanks,
bin
gcc/testsuite/ChangeLog
2017-05-11  Bin Cheng  <bin.cheng@arm.com>

	* gcc.dg/tree-ssa/ivopt_mult_4.c: Explicitly check comparison
	on pointer should not be replaced.