Sarah Thompson
2007-Jul-25 22:57 UTC
[LLVMdev] Instruction::mayWriteToMemory() -- is there a logical equivalent for reads?
The Instruction::mayWriteToMemory() member function is quite useful (I'm currently writing code that will break up basic blocks at read/write instructions). Is there a safe way to do the same thing for reads from memory? It's easy enough to check for the relevant instructions, but I thought this might be a nice-to-have in a future version because it separates code like mine from needing to know too much about the instructions it is manipulating (which is a good thing from a future portability point of view, as well as being logically cleaner). [s]
Chris Lattner
2007-Jul-26 04:56 UTC
[LLVMdev] Instruction::mayWriteToMemory() -- is there a logical equivalent for reads?
On Wed, 25 Jul 2007, Sarah Thompson wrote:> The Instruction::mayWriteToMemory() member function is quite useful (I'm > currently writing code that will break up basic blocks at read/write > instructions). Is there a safe way to do the same thing for reads from > memory? It's easy enough to check for the relevant instructions, but IYep, the alias analysis interface will provide this information for you, -Chris -- http://nondot.org/sabre/ http://llvm.org/
Seemingly Similar Threads
- [LLVMdev] Instruction->mayReadFromMemory
- [LLVMdev] Instruction->mayReadFromMemory
- [LLVMdev] All CallInsts mayHaveSideEffects
- [LLVMdev] all LLVM Instructions that may write to memory -- other than StoreInst?
- [LLVMdev] all LLVM Instructions that may write to memory -- other than StoreInst?