Blog

Overview

C++ Memory Model

June 6, 2016

/

Since C++11, C++ has a memory model. It is the foundation for multithreading. Without it, multithreading…

async

The Special Futures

June 6, 2016

/

The parent of a thread has to take care of their child. The parent can wait until his child is done or…

promiseFuture

Promise and Future

June 5, 2016

/

With std::promise and std::future, you have full control over the task. Full control over the task A…

BackgroundCpp

Modernes C++

June 4, 2016

/

This page is the starting point for my blog Modernes C++. A simple overview of my existing and upcoming…

packagedTask

Asynchronous Callable Wrappers

June 3, 2016

/

std::packaged_task enables you to write a simple wrapper for a callable, which you can invoke later. std::packaged_task To…

async

Asynchronous Function Calls

May 26, 2016

/

std:.async feels like an asynchronous function call. Under the hood std::async is a task. One, which…

tasksEng

Tasks

May 21, 2016

/

Tasks were one of the latest additions to the C++11 standard. They give you a better abstraction than…

conditionVariable

Condition Variables

May 17, 2016

/

Condition variables allow us to synchronize threads via notifications. So, you can implement workflows…

threadLocal

Thread-Local Data

May 16, 2016

/

By using the keyword thread_local, you define the thread local data. Thread-local can easily be…

callOnce

Thread-Safe Initialization of Data

May 15, 2016

/

The story is simple if the data is not modified when shared between threads. The data has only to be…

deadlockResolved

Prefer Locks to Mutexes

May 12, 2016

/

If the previous post showed something, it's that you should use mutexes with great care. That's why you…

Deadlock

The Risks of Mutexes

May 10, 2016

/

The usage of mutexes seems extremely simple. There is a critical section in the code that a single thread…

Latest news

Hazard Pointers in C++26May 5, 2025 - 11:12 am
Hazard pointers provide garbage collection in C++ and solve the ABA problem. First of all. What is a hazard pointer? Proposal P2530R3 gives a nice explanation: A hazard pointer is a single-writer multi-reader pointer that can be owned by at most one thread at any time. Only the owner of the hazard pointer can set […]
A Lock-Free Stack: A Hazard Pointer Implementation Explained IIApril 7, 2025 - 11:11 am
In my last post, I started to explain a hazard pointer implementation: A Lock-Free Stack: A Hazard Pointer Implementation Explained I. Today, I will continue to explain the implementation. The Retire List The retire list has the public member functions isInUse, addNode, and deleteUnusedNodes. Additionally, it has the inner class RetireNode, an atomic member of […]
A Lock-Free Stack: A Hazard Pointer Implementation Explained IMarch 24, 2025 - 11:37 am
In my last post, I presented a hazard pointer implementation: A Lock-Free Stack: A Hazard Pointer Implementation. Today, I will explain the implementation. MyNode is a class template, parametrized by the type it holds: data. MyNode models the concept Node. template <typename T> concept Node = requires(T a) { {T::data}; { *a.next } -> std::same_as<T&>; […]
A Lock-Free Stack: A Hazard Pointer ImplementationMarch 10, 2025 - 11:42 am
Hazard Pointers solve all issues of the previous implementation: A Lock-Free Stack: A Simple Garbage Collector. From one Week to two Weeks You may have already noticed. I will change my blog publishing frequency from one to two weeks in the future. Writing a post using your voice is exceptionally exhausting and time-consuming. Hazard Pointers […]
A Lock-Free Stack: A Simple Garbage CollectorFebruary 24, 2025 - 11:58 am
My next lock-free stack includes a simple garbage collector. I discussed the concurrent execution of more than one topAndPush call is a Race Condition. I can safely delete a node if not more than one topAndPush call is executing concurrently. This observation is crucial for solving this memory leak issue: I store removed nodes on […]
A Lock-Free Stack: Atomic Smart PointerFebruary 17, 2025 - 11:47 am
The easiest way to solve this memory leak issue from the last post is to use a std::shared_ptr. Atomic Smart Pointer There are two ways to apply atomic operations on a std::shared_ptr: In C++11, you can use the free atomic functions on std::shared_ptr. With C++20, you can use atomic smart pointers. C++11 Using atomic operations […]