------- Additional Comments From amylaar at gcc dot gnu dot org 2005-03-10
04:24 -------
(In reply to comment #3)
> I'm taking a look at the uses of MEM_READONLY_P, though I'm not
> sure which one has the similar issue. It looks that modified_in_p
> has the same problem with modified_between_p.
Yes, that's also the one I spotted first. But it's simple to find more:
grep tells us alias.c has some MEM_READONLY_P. Bingo, the first hit is
another instance: true_dependence does:
if (MEM_READONLY_P (x))
return 0;
without checking if x contains a MEM that is dependent (possible if the
target supports memory-indirect addressing, e.g. m68020)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20331
