Searched refs:MAY_WRITE (Results 1 – 6 of 6) sorted by relevance
14 ; The MAY_WRITE in reduction.exit.true avoids that anything can be mapped to15 ; A[j] because it would be overwritten by that MAY_WRITE just before the final16 ; MUST_WRITE. Also nothing can be map to the MAY_WRITE itself because it is a17 ; MAY_WRITE.
14 ; The MAY_WRITE in reduction.for.true conflict with a write of %phi to15 ; A[j] if %phi would be mapped to it. Being a MAY_WRITE avoids being target18 ; TODO: There is actually no reason why these conflict. The MAY_WRITE is an
451 MAY_WRITE = 0x3, enumerator762 bool isMayWrite() const { return AccType == MemoryAccess::MAY_WRITE; } in isMayWrite()
1828 auto AccType = ReadOnly ? MemoryAccess::READ : MemoryAccess::MAY_WRITE; in buildAccessCallInst()1887 AccType = MemoryAccess::MAY_WRITE; in buildAccessSingleDim()2297 AccType = MemoryAccess::MAY_WRITE; in addMemoryAccess()
957 case MAY_WRITE: in print()
2661 return isl_union_map_union(getTaggedAccesses(MemoryAccess::MAY_WRITE), in getTaggedMayWrites()