search for: intrwriteonly

...it such a memory addressing model into the ArgMemOnly logic that would be appreciated, but from my reading of the code it appears that trying to make ArgMemOnly work with this would be a rather large project which we don't really have the resources to tackle right now. Why am I pushing for IntrWriteOnly? I suspect the merely IntrWriteOnly without a functional ArgMemOnly does not provide a lot of opportunity for optimization at the IR level. However, the codegen backend does understand the resulting hardware instructions, which are marked mayLoad = 0, mayStore = 1, hasSideEffects = 0. Having m...

...odel > into the ArgMemOnly logic that would be appreciated, but from my > reading of the code it appears that trying to make ArgMemOnly work > with this would be a rather large project which we don't really have > the resources to tackle right now. > > Why am I pushing for IntrWriteOnly? > > I suspect the merely IntrWriteOnly without a functional ArgMemOnly > does not provide a lot of opportunity for optimization at the IR level. I think this is not entirely true. In particular, it gives us a way to model things like memset and memset_16 by combining InstrWriteOnly and...

Hi, I'd like to draw your attention to http://reviews.llvm.org/D18291, in which I propose a new intrinsic property for intrinsics that are lowered to instructions that mayStore, but are neither mayLoad nor hasSideEffects. This is relevant for AMDGPU, where we have store instructions that don't operate on pointers. The codegen backend understands these perfectly well as stores, and so