search for: atomic_fetch_add

...> compare-and-swap. This is true for at least ARMv5, SPARCv8, and Intel > 80386. When your minimum CPU is set to such a cpu model, all atomic > operations must be done via libcall -- it's not acceptable for > atomic_store to emit an atomic "store" instruction, but > atomic_fetch_add to require a libcall which gets implemented with a > lock. If that were to happen, then atomic_fetch_add could not actually > be made atomic versus a simultaneous atomic_store. > > > So anyhow, there's basically two paths I think we could take for > cleanup. I like "Al...

...sing any way to do an atomic compare-and-swap. This is true for at least ARMv5, SPARCv8, and Intel 80386. When your minimum CPU is set to such a cpu model, all atomic operations must be done via libcall -- it's not acceptable for atomic_store to emit an atomic "store" instruction, but atomic_fetch_add to require a libcall which gets implemented with a lock. If that were to happen, then atomic_fetch_add could not actually be made atomic versus a simultaneous atomic_store. So anyhow, there's basically two paths I think we could take for cleanup. I like "Alternative A" below better,...

...; atomic compare-and-swap. This is true for at least ARMv5, SPARCv8, > and Intel 80386. When your minimum CPU is set to such a cpu model, > all atomic operations must be done via libcall -- it's not > acceptable for atomic_store to emit an atomic "store" instruction, > but atomic_fetch_add to require a libcall which gets implemented > with a lock. If that were to happen, then atomic_fetch_add could not > actually be made atomic versus a simultaneous atomic_store. > > > > > So anyhow, there's basically two paths I think we could take for > cleanup. I li...

...ns/atomics.types.operations.req/atomic_compare_exchange_weak_explicit.pass.cpp libc++ :: std/atomics/atomics.types.oper 1 warning(s) in tests. ations/atomics.types.operations.req/atomic_exchange_explicit.pass.cpp libc++ :: std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_fetch_add.pass.cpp libc++ :: std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_fetch_add_explicit.pass.cpp libc++ :: std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_fetch_and.pass.cpp libc++ :: std/atomics/atomics.types.operations/atomics.types.o...

Dear testers, Release Candidate 3 has just been tagged [1]. Please build, test, and upload to the sftp. If there are no regressions from previous release candidates, this will be the last release candidate before the final release. Release notes can still go into the branch. Thanks again for all your work! Hans [1] http://lists.llvm.org/pipermail/llvm-branch-commits/2016-February/009866.html

...xchange_weak_explicit.pass.cpp > libc++ :: std/atomics/atomics.types.oper > 1 warning(s) in tests. > ations/atomics.types.operations.req/atomic_exchange_explicit.pass.cpp > libc++ :: std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_fetch_add.pass.cpp > libc++ :: std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_fetch_add_explicit.pass.cpp > libc++ :: std/atomics/atomics.types.operations/atomics.types.operations.req/atomic_fetch_and.pass.cpp > libc++ :: std/atomics/atom...

Hi, I've tagged 3.8.1-rc1, testers can begin testing. -Tom