std::experimental::flex_barrier::arrive_and_wait

 

C++

Language

Standard Library Headers

Freestanding and hosted implementations

Named requirements

Language support library

Concepts library (C++20)

Diagnostics library

Utilities library

Strings library

Containers library

Iterators library

Ranges library (C++20)

Algorithms library

Numerics library

Input/output library

Localizations library

Regular expressions library (C++11)

Atomic operations library (C++11)

Thread support library (C++11)

Filesystem library (C++17)

Technical Specifications

 

Technical specifications

Filesystem library (filesystem TS)

Library fundamentals (library fundamentals TS)

Library fundamentals 2 (library fundamentals 2 TS)

Extensions for parallelism (parallelism TS)

Extensions for parallelism 2 (parallelism TS v2)

Extensions for concurrency (concurrency TS)

Concepts (concepts TS)

Ranges (ranges TS)

Special mathematical functions (special math TR)

 

Extensions for concurrency

std::future extensions

experimental::future

experimental::shared_future

experimental::when_all

experimental::when_any

experimental::make_ready_future

experimental::make_exceptional_future

Latches and barriers

experimental::latch

experimental::barrier

experimental::flex_barrier

Atomic smart pointers

experimental::atomic_shared_ptr

experimental::atomic_weak_ptr

 

std::experimental::flex_barrier

flex_barrier::flex_barrier

flex_barrier::~flex_barrier

flex_barrier::arrive_and_wait

flex_barrier::arrive_and_drop

 

void arrive_and_wait();		(concurrency TS)

Blocks and arrives at the flex_barrier's synchronization point.

The behavior is undefined if the calling thread is not in the set of participating threads of this flex_barrier.

Calls to arrive_and_wait synchronizes with the start of the completion phase of the flex_barrier. The completion of the completion phase synchronizes with the return from the call.

Calls to arrive_and_drop and arrive_and_wait never introduce data races with themselves or each other.

Notes

It is safe for a thread to call either arrive_and_wait() or arrive_and_drop() immediately on return from this call (provided that the function object for the completion phase did not return zero). It's not necessary to ensure that all blocked threads have exited arrive_and_wait() before a thread calls it again.

The completion phase executes the function object specified when the flex_barrier was constructed. If it returns -1, the set of participating threads is unchanged; otherwise, the set of participating threads is a new set with the size equal to the return value N, and consists of the next N threads to arrive at the synchronization point. If N == 0, the flex_barrier can only be destroyed.

The initial set of participating threads for a flex_barrier constructed for num_threads threads is the first num_threads to arrive at its synchronization point.

Exceptions

Throws nothing.

See also

arrive_and_drop

arrive at the synchronization point and remove the current thread from the set of participating threads (public member function)