search for: __atomic_fetch_add

Displaying 10 results from an estimated 10 matches for "__atomic_fetch_add".

Did you mean: __atomic_fetch_add_4
2013 May 10
0
[LLVMdev] __atomic_fetch_add on ARM
> This seems to be the problem in my box, and Benjamin's hint did solve the > problem (setting MaxAtomicInlineWidth). However, I'm not sure what relation > that variable has to do with choosing library calls or not. If it's just a > matter of variable sizes (allowing direct atomic calls on 64-bit VFP > instructions), that it's possible that the fix is correct. For
2013 May 10
0
[LLVMdev] __atomic_fetch_add on ARM
I think this is two bugs in one: * In ABIs that don't use external functions for atomics (linux hard float at least), we incorrectly decide to use function calls. * In ABIs that do use external function calls (non hard float linux?), we don't have code to actually generate the calls. See the thread in http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20130415/078021.html. The
2013 May 10
2
[LLVMdev] __atomic_fetch_add on ARM
On 10 May 2013 16:21, Rafael EspĂ­ndola <rafael.espindola at gmail.com> wrote: > * In ABIs that don't use external functions for atomics (linux hard > float at least), we incorrectly decide to use function calls. > This seems to be the problem in my box, and Benjamin's hint did solve the problem (setting MaxAtomicInlineWidth). However, I'm not sure what relation that
2013 May 09
2
[LLVMdev] __atomic_fetch_add on ARM
Hi Benjamin, Several people (including me) are hitting this bug on ARM: http://llvm.org/bugs/show_bug.cgi?id=15429 >From my investigations it happens on Ubuntu 12.10+ but not on 12.04. From Tom Gail's, it happens with --enable-optimized and doesn't without. You seem to have a clue on what that happens, can you shed some light on the matter? I see this error when self-hosting Clang
2013 Oct 02
2
C++ debugging help needed
...> library(mixOmics) > example(pca) This crashes with messages like this: Program received signal SIGSEGV, Segmentation fault. 0x00007ffff28aafd9 in __exchange_and_add (__mem=0x7f7fffff7f7ffff7, __val=<optimized out>) at /usr/include/c++/4.7/ext/atomicity.h:48 48 { return __atomic_fetch_add(__mem, __val, __ATOMIC_ACQ_REL); } The call stack ends with this: #0 0x00007ffff28aafd9 in __exchange_and_add (__mem=0x7f7fffff7f7ffff7, __val=<optimized out>) at /usr/include/c++/4.7/ext/atomicity.h:48 #1 __exchange_and_add_dispatch (__mem=0x7f7fffff7f7ffff7, __val=<optimize...
2013 Jan 06
0
[LLVMdev] Failure building llvm/clang from source using binary clang package on Fedora 17
...ng.h:4013: /usr/bin/../lib/gcc/x86_64-redhat-linux/4.7.2/../../../../include/c++/4.7.2/ext/atomicity.h:48:: 45:In file included from error: use of/usr/bin/../lib/gcc/x86_64-redhat-linux/4.7.2/../../../../include/c++/4.7.2/string undeclared identifier '__ATOMIC_ACQ_REL' { return __atomic_fetch_add(__mem, __val, __ATOMIC_ACQ_REL); }: If I build with gcc, there are no problems. The 3.0-4 distribution of clang says that it was updated for gcc 4.7.2.
2019 Dec 15
1
Bug: indexer-worker segfaults with fts_xapian 1.2.5
...ot/indexer-worker'. Program terminated with signal 11, Segmentation fault. #0 0x00007f30f7ad056d in __exchange_and_add (__val=-1, __mem=0xfffffffffffffff8) at /usr/src/debug/gcc-4.8.5-20150702/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/ext/atomicity.h:49 49 { return __atomic_fetch_add(__mem, __val, __ATOMIC_ACQ_REL); } (gdb) bt full #0 0x00007f30f7ad056d in __exchange_and_add (__val=-1, __mem=0xfffffffffffffff8) at /usr/src/debug/gcc-4.8.5-20150702/obj-x86_64-redhat-linux/x86_64-redhat-linux/libstdc++-v3/include/ext/atomicity.h:49 No locals. #1 __exchange_and_add_dispatch...
2012 May 29
3
[LLVMdev] make error
...de/c++/4.7.0/ios:42: In file included from /usr/lib/gcc/i686-pc-linux-gnu/4.7.0/../../../../include/c++/4.7.0/bits/ios_base.h:40: /usr/lib/gcc/i686-pc-linux-gnu/4.7.0/../../../../include/c++/4.7.0/ext/atomicity.h:48:45: error: use of undeclared identifier '__ATOMIC_ACQ_REL' { return __atomic_fetch_add(__mem, __val, __ATOMIC_ACQ_REL); } ^ /usr/lib/gcc/i686-pc-linux-gnu/4.7.0/../../../../include/c++/4.7.0/ext/atomicity.h:52:38: error: use of undeclared identifier '__ATOMIC_ACQ_REL' { __atomic_fetch_add(__mem, __val, __ATOMIC_ACQ_REL); }...
2012 May 29
0
[LLVMdev] make error
...file included from > /usr/lib/gcc/i686-pc-linux-gnu/4.7.0/../../../../include/c++/4.7.0/bits/ios_base.h:40: > /usr/lib/gcc/i686-pc-linux-gnu/4.7.0/../../../../include/c++/4.7.0/ext/atomicity.h:48:45: > error: use of undeclared identifier > '__ATOMIC_ACQ_REL' > { return __atomic_fetch_add(__mem, __val, __ATOMIC_ACQ_REL); } > ^ > /usr/lib/gcc/i686-pc-linux-gnu/4.7.0/../../../../include/c++/4.7.0/ext/atomicity.h:52:38: > error: use of undeclared identifier > '__ATOMIC_ACQ_REL' > { __atomic_fetch_add(__mem, __val,...
2012 May 24
1
[LLVMdev] vmkit: Getting Started
...n file included from /usr/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.7.0/../../../../include/c++/4.7.0/bits/ios_base.h:40: /usr/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.7.0/../../../../include/c++/4.7.0/ext/atomicity.h:48:45: error: use of undeclared identifier '__ATOMIC_ACQ_REL' { return __atomic_fetch_add(__mem, __val, __ATOMIC_ACQ_REL); } ^ /usr/bin/../lib/gcc/x86_64-unknown-linux-gnu/4.7.0/../../../../include/c++/4.7.0/ext/atomicity.h:52:38: error: use of undeclared identifier '__ATOMIC_ACQ_REL' { __atomic_fetch_add(__mem, __val, __ATOMIC_ACQ_R...