Re: [014/nnn] poly_int: indirect_refs_may_alias_p

2017-11-20 Thread Jeff Law
On 11/20/2017 06:00 AM, Richard Sandiford wrote: > Jeff Law writes: >> On 10/23/2017 11:05 AM, Richard Sandiford wrote: >>> This patch makes indirect_refs_may_alias_p use ranges_may_overlap_p >>> rather than ranges_overlap_p. Unlike the former, the latter can handle >>> negative offsets, so the f

Re: [014/nnn] poly_int: indirect_refs_may_alias_p

2017-11-20 Thread Richard Sandiford
Jeff Law writes: > On 10/23/2017 11:05 AM, Richard Sandiford wrote: >> This patch makes indirect_refs_may_alias_p use ranges_may_overlap_p >> rather than ranges_overlap_p. Unlike the former, the latter can handle >> negative offsets, so the fix for PR44852 should no longer be necessary. >> It can

Re: [014/nnn] poly_int: indirect_refs_may_alias_p

2017-11-17 Thread Jeff Law
On 10/23/2017 11:05 AM, Richard Sandiford wrote: > This patch makes indirect_refs_may_alias_p use ranges_may_overlap_p > rather than ranges_overlap_p. Unlike the former, the latter can handle > negative offsets, so the fix for PR44852 should no longer be necessary. > It can also handle offset_int,

[014/nnn] poly_int: indirect_refs_may_alias_p

2017-10-23 Thread Richard Sandiford
This patch makes indirect_refs_may_alias_p use ranges_may_overlap_p rather than ranges_overlap_p. Unlike the former, the latter can handle negative offsets, so the fix for PR44852 should no longer be necessary. It can also handle offset_int, so avoids unchecked truncations to HOST_WIDE_INT. 2017