search for: __c11_atomic_

If you check the Clang list (cfe-dev-list) the issue dealing with atomics for gcc-4.7 has been settled. I can verify this on Debian Linux using gcc-4.7 that clang/clang++ builds and no long fails when compiling a simple HelloWorld program. Atomics for c++ are now recognized as __c11_atomic_* and it builds cleanly from what i've tested. I presently don't have a 10.7 box to test against trunk, but those errors are now gone from Linux. The thread to read: http://lists.cs.uiuc.edu/pipermail/cfe-dev/2012-April/020686.html - Marc On 04/12/2012 10:44 AM, Andrea Bigagli wrote: &...

Hi, the subject says it all... After some experimenting, I got a bit confused as far as what the proper thing to do might be.... I build llvm/clang from trunk sources on OSX Lion 10.7.3 (i.e. x86_64-apple-darwin11.3.0 to speak GNU's platform-ese) where I also have successfully built a fsf-gcc 4.6.2 (and lately a 4.7 for that matter) from sources. Now, I think I understand that by playing

...nment and target, lower either to a libcall to a > "standardized-by-GCC > <https://gcc.gnu.org/wiki/Atomic/GCCMM/LIbrary>" __atomic_* > library function (implemented by libatomic), or, to the atomic IR > instructions. (Also covered by the same code is the __c11_atomic_* > builtins, which are almost-identical clang-specific aliases of the > __atomic_* builtins.) > 3. There's the C11 "_Atomic" type modifier and some OpenMP stuff, > which clang lowers into atomic IR or libcalls to __atomic_* > library functions, via almo...

...ang will, depending on size and alignment and target, lower either to a libcall to a "standardized-by-GCC <https://gcc.gnu.org/wiki/Atomic/GCCMM/LIbrary>" __atomic_* library function (implemented by libatomic), or, to the atomic IR instructions. (Also covered by the same code is the __c11_atomic_* builtins, which are almost-identical clang-specific aliases of the __atomic_* builtins.) There's the C11 "_Atomic" type modifier and some OpenMP stuff, which clang lowers into atomic IR or libcalls to __atomic_* library functions, via almost completely separate code from #2. (Note: d...

...iltins, which clang will, > depending on size and alignment and target, lower either to a > libcall to a " standardized-by-GCC " __atomic_* library function > (implemented by libatomic), or, to the atomic IR instructions. > (Also covered by the same code is the __c11_atomic_* builtins, > which are almost-identical clang-specific aliases of the > __atomic_* builtins.) > 3. There's the C11 "_Atomic" type modifier and some OpenMP stuff, > which clang lowers into atomic IR or libcalls to __atomic_* > library functions, via a...