search for: __atomic_compare_exchange

...nt<2> [ID=4] 0x30cc518: i32 = X86ISD::WrapperRIP 0x30ccab8 [ID=6] 0x30ccab8: i32 = TargetJumpTable<0> [ID=3] 0x30cc6c8: i32 = undef [ID=2] 0x30cc518: i32 = X86ISD::WrapperRIP 0x30ccab8 [ID=6] 0x30ccab8: i32 = TargetJumpTable<0> [ID=3] In function: __atomic_compare_exchange clang: error: clang frontend command failed with exit code 70 (use -v to see invocation) clang version 3.4 (trunk) Target: x86_64-pc-linux-gnux32 Thread model: posix This is what happens when compiling compiler-rt with -m64 or -mx32, exact same error without my patches (where -mx32 is supported)....

Ah, I've replied in a different thread already. What Dmitri says - If you're interesting in only building the Clang on x32 host, you may avoid checking out compiler-rt repo for now. On Thu, Aug 22, 2013 at 10:59 AM, Dmitri Gribenko <gribozavr at gmail.com>wrote: > On Wed, Aug 21, 2013 at 11:04 PM, Steven Newbury <steve at snewbury.org.uk> > wrote: > > I've

...Except for one case: clang will still need to emit library calls itself for data not aligned naturally for its size. The LLVM atomic instructions currently will not handle unaligned data, but unaligned data is allowed for the four "slab of memory" builtins (__atomic_load, __atomic_store, __atomic_compare_exchange, and __atomic_exchange). A3) In LLVM, add "align" attributes to cmpxchg and atomicrmw, and allow specifying "align" values for "load atomic" and "store atomic" (where the attribute currently exists but cannot be used). LLVM will then be able to lower misalig...

...ang will still need to emit library calls > itself for data not aligned naturally for its size. The LLVM atomic > instructions currently will not handle unaligned data, but unaligned > data is allowed for the four "slab of memory" builtins (__atomic_load, > __atomic_store, __atomic_compare_exchange, and __atomic_exchange). > > A3) In LLVM, add "align" attributes to cmpxchg and atomicrmw, and > allow specifying "align" values for "load atomic" and "store atomic" > (where the attribute currently exists but cannot be used). LLVM will > th...

...: clang will still need to emit library calls > itself for data not aligned naturally for its size. The LLVM atomic > instructions currently will not handle unaligned data, but unaligned > data is allowed for the four "slab of memory" builtins > (__atomic_load, __atomic_store, __atomic_compare_exchange, and > __atomic_exchange). > > > A3) In LLVM, add "align" attributes to cmpxchg and atomicrmw, and > allow specifying "align" values for "load atomic" and "store atomic" > (where the attribute currently exists but cannot be used). LLVM wil...