Krzysztof Parzyszek 53d7c42c6d [Hexagon] Generate correct runtime check when recognizing memmove ... The check (assuming positive stride) for validity of memmove should be (a) the destination is at a lower address than the source, or (b) the distance between the source and destination is greater than or equal the number of bytes copied. For the second part it is sufficient to assume that the destination is at a higher address, since the opposite case is covered by (a). The distance calculation was previously done by subtracting the pointers in the wrong order. llvm-svn: 311650		2017-08-24 11:59:53 +00:00
..
hexagon-memmove1.ll
hexagon-memmove2.ll
lcssa.ll
memmove-rt-check.ll	[Hexagon] Generate correct runtime check when recognizing memmove	2017-08-24 11:59:53 +00:00
nullptr-crash.ll
pmpy-infinite-loop.ll	[Hexagon] Avoid infinite loops in HexagonLoopIdiomRecognition	2017-03-23 23:01:22 +00:00
pmpy-long-loop.ll	[Hexagon] Handle long-running simplification loop in idiom recognition	2017-06-01 18:00:47 +00:00
pmpy-mod.ll	Recommit r298282 with fixes for memory allocation/deallocation	2017-03-21 17:09:27 +00:00
pmpy-shiftconv-fail.ll	[Hexagon] Stop pmpy recognition when shift conversion fails	2017-06-13 13:51:49 +00:00
pmpy.ll