search for: intrwriteargmem

...peration. Is there a better way to do this? > > Crazy idea: how about an intrinsic just after the load or store of > interest? > It would be a sort of opposite of prefetch, saying "i'm not going to be > using the memory at this address for a while". It could use > IntrWriteArgMem like the regular prefetch does, which is usually > sufficient to keep it from wandering off, though it is a little > stronger than > is strictly necessary. Does before vs. after matter for IntrWriteArgMem? What does that do anyway? > The other alternative is something like llvm.x86.s...

...gt; intrinsic-followed-by-operation. Is there a better way to do this? Crazy idea: how about an intrinsic just after the load or store of interest? It would be a sort of opposite of prefetch, saying "i'm not going to be using the memory at this address for a while". It could use IntrWriteArgMem like the regular prefetch does, which is usually sufficient to keep it from wandering off, though it is a little stronger than is strictly necessary. The other alternative is something like llvm.x86.sse.movnt.ps and friends. Dan

On Saturday 01 August 2009 15:12, Dan Gohman wrote: > LoadSDNode, which inherits from MemSDNode is the largest > SDNode. With the current SDNode allocation strategy, making it > bigger will increase the allocation needed for all nodes. Ok. > > new (N) LoadSDNode(..., isVolatile|isNonTemporal); > > > > Thoughts? > > This sounds reasonable. I'd suggest