History log of /external/clang/test/CodeGen/2010-01-13-MemBarrier.c
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
651f13cea278ec967336033dd032faef0e9fc2ec 24-Apr-2014 Stephen Hines <srhines@google.com> Updated to Clang 3.5a.

Change-Id: I8127eb568f674c2e72635b639a3295381fe8af82
/external/clang/test/CodeGen/2010-01-13-MemBarrier.c
c83b975f1fb9d11e10b5aa25029ae9bb5fa80e07 07-Sep-2011 Eli Friedman <eli.friedman@gmail.com> Switch clang over to using fence/atomicrmw/cmpxchg instead of the intrinsics (which will go away). LLVM CodeGen does almost exactly the same thing with these and the old intrinsics, so I'm reasonably confident this will not break anything.

There are still a few issues which need to be resolved with code generation for atomic load and store, so I'm not converting the places which need those for now.

I'm not entirely sure what to do about __builtin_llvm_memory_barrier: the fence instruction doesn't expose all the possibilities which can be expressed by __builtin_llvm_memory_barrier. I would appreciate hearing from anyone who is using this intrinsic.



git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@139216 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/CodeGen/2010-01-13-MemBarrier.c
3883e66cfd55de70d89831cf26f9ae53931d11d3 27-Jul-2011 Eric Christopher <echristo@apple.com> Migrate most of the rest of test/FrontendC from llvm and migrate
most of them to FileCheck.


git-svn-id: https://llvm.org/svn/llvm-project/cfe/trunk@136159 91177308-0d34-0410-b5e6-96231b3b80d8
/external/clang/test/CodeGen/2010-01-13-MemBarrier.c