[llvm-commits] [llvm] r122801 - /llvm/trunk/lib/Transforms/Scalar/CodeGenPrepare.cpp
zwarich at apple.com
Wed Jan 5 20:42:08 CST 2011
On Jan 5, 2011, at 6:40 PM, Jakob Stoklund Olesen wrote:
> On Jan 5, 2011, at 6:16 PM, Cameron Zwarich wrote:
>> However, we could expand the inline assembly on the first pass and then do OptimizeInlineAsmInst and OptimizeCallInst on subsequent visits via the worklist.
> Maybe you could go even further. It seems to me that only OptimizeNoopCopyExpression, OptimizeExtUses, and OptimizeCmpExpression can change anything on a second pass, but perhaps the AddressingModeMatcher used by OptimizeMemoryInst could also be affected?
There are definitely memory inst optimizations triggered by later passes, although I haven't looked at any in particular.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-commits