On Sun, Oct 12, 2014 at 7:44 PM, Uros Bizjak <ubiz...@gmail.com> wrote:
>>> Right. And my question is what happens if we aren't as aggressive here. >>> What happens if before this check we return nonzero if X or Y is a VALUE? >>> Do we then get into memrefs_conflict_p and does it do the right thing? >> >> Following patch just after AND detection in base_alias_check fixes the >> testcase from PR: [...] > It looks to me that the code that handles AND addresses in > base_alias_check is not prepared to handle VALUES correctly. The further analysis and proposed patch follows up at [1]. [1] https://gcc.gnu.org/ml/gcc-patches/2014-10/msg01209.html Uros.
