nv50/ir: adjust overlapping logic to take fileIndex-relative offsets
authorIlia Mirkin <imirkin@alum.mit.edu>
Sat, 24 Jun 2017 21:09:20 +0000 (17:09 -0400)
committerIlia Mirkin <imirkin@alum.mit.edu>
Tue, 27 Jun 2017 00:24:19 +0000 (20:24 -0400)
commit7d56ae5eb2e32e88c90261d6782890ce0c524e7d
tree56fdd21fabdd72c86587d853084d7c39069cefc6
parent55a8c117051406ff80166d365e832ff99b90d1a8
nv50/ir: adjust overlapping logic to take fileIndex-relative offsets

If the fileIndex is different, that means they are in logically
different spaces. However if there's also a relative offset, then they
could end up pointing at the same spot again.

Also add a note about potential for multiple buffers to overlap even if
they're at different file indexes. However that's potentially lowered
away by the point that this logic hits.

Not known to fix any specific application or test.

Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu>
Reviewed-by: Samuel Pitoiset <samuel.pitoiset@gmail.com>
src/gallium/drivers/nouveau/codegen/nv50_ir_peephole.cpp