search for: instrwriteonly

...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 ArgMemOnly. It's not quite as powerful as having a writeonly argument attribute, but it's better than where we are today. > > However, the codegen backend does understand the resulting hardware > instructions, which are marked mayLoad = 0, mayStore = 1, > hasSideEffects...

On 19.03.2016 14:47, Philip Reames wrote: > I'm generally in support of this change. I haven't looked at the patch > yet, but the direction seems worthwhile. > > Note that we already have a writeonly predicate in a few places in the > code (BasicAA being one). If we do introduce the new intrinsic > property, we should refactor all of these places to use the new >