The Atomic Flag
Atomics guarantee two characteristics. On the one hand, they are atomic, on the other, they provide synchronization and order constraints on the program execution.
Author Archive for: admin
Entries by Rainer Grimm
Thread Synchronization with Condition Variables or Tasks
In case you use promise and future to synchronize threads, they have much in common with condition variables. But most of the time, tasks are the better choice.
C++ Memory Model
Since C++11, C++ has a memory model. It is the foundation for multithreading. Without it, multithreading is not well defined.
The Special Futures
The parent of a thread has to take care of their child. The parent can wait until his child is done or detach himself from his child. But that is not new. But that will not hold for std::async. The big charm of std::async is that the parent has not taken care of his child.
Promise and Future
With std::promise and std::future, you have full control over the task.
Modernes C++
This page is the starting point for my blog Modernes C++. A simple overview of my existing and upcoming posts.
Asynchronous Callable Wrappers
std::packaged_task enables you to write a simple wrapper for a callable, which you can invoke later.
Asynchronous Function Calls
std:.async feels like an asynchronous function call. Under the hood std::async is a task. One, which is extremely easy to use.
Tasks
Tasks were one of the latest additions to the C++11 standard. They give you a better abstraction than threads. In the general case, they should be your first choice.
Condition Variables
Condition variables allow us to synchronize threads via notifications. So, you can implement workflows like sender/receiver or producer/consumer. In such a workflow, the receiver waits for the sender’s notification. If the receiver gets the notification, it continues its work.