[llvm-commits] [llvm] r99928 - in /llvm/trunk: include/llvm/ include/llvm/CodeGen/ include/llvm/Support/ include/llvm/Target/ include/llvm/Transforms/Utils/ lib/CodeGen/SelectionDAG/ lib/Target/ARM/ lib/Target/PowerPC/ lib/Target/X86/ lib/Target/XCore/ lib/Transforms/InstCombine/ lib/Transforms/Scalar/ lib/Transforms/Utils/ lib/VMCore/ test/Analysis/BasicAA/ test/Transforms/InstCombine/ test/Transforms/MemCpyOpt/ test/Transforms/SimplifyLibCalls/ test/Verifier/

Duncan Sands baldrick at free.fr
Tue Mar 30 22:33:07 PDT 2010


Hi Chris,

>> I'm trying to imagine situations in which a volatile mem* call is useful, but I
>> didn't come up with anything very convincing yet.  Can you please explain what
>> you have in mind.
>
> volatile struct foo X, Y;
>
> X = Y;
>
> Should lower to a 'volatile memcpy'.

shouldn't it load to a series of field by field volatile copies?

Ciao,

Duncan.



More information about the llvm-commits mailing list