Re: [100/nnn] poly_int: memrefs_conflict_p

2017-12-05 Thread Jeff Law
On 10/23/2017 11:40 AM, Richard Sandiford wrote: > The xsize and ysize arguments to memrefs_conflict_p are encode such > that: > > - 0 means the size is unknown > - >0 means the size is known > - <0 means that the negative of the size is a worst-case size after > alignment > > In other words, t

[100/nnn] poly_int: memrefs_conflict_p

2017-10-23 Thread Richard Sandiford
The xsize and ysize arguments to memrefs_conflict_p are encode such that: - 0 means the size is unknown - >0 means the size is known - <0 means that the negative of the size is a worst-case size after alignment In other words, the sign effectively encodes a boolean; it isn't meant to be taken l