Blog

An Overview Of C++26: The Library – Math

September 9, 2024

The most interesting feature of the new C++26 standard library is its improved math support. std::submdspan std::submdspan…

An Overview of C++26: The Library

September 2, 2024

In my last post, I overviewed C++26's core language. Today, I continue with the library. To make…

An Overview of C++26: Core Language

August 26, 2024

C++26 has a lot to offer. Let me directly jump in and give you an overview. This image gives…

C++26: The Next C++ Standard

August 19, 2024

/

C++26 will be the next C++ standard after C++23. This new standard significantly improves C++ and is…

My ALS Journey (13/n): Next Steps

August 13, 2024

Ice Bucket Challenge The Ice Bucket Challenge, sometimes called the ALS Ice Bucket Challenge,…

Table of Content

August 12, 2024

C++23: This and That

August 12, 2024

I have already written 10 posts about C++23. Today, I want to discuss the features I forgot in the first…

Feature Testing Macros

August 5, 2024

The feature testing macros is a relatively unknown feature in C + + 20. They give you the definitive…

My ALS Journey (12/n): My Legacy

July 25, 2024

Today, I want to give you a rough idea, how I plan my next year's as a teacher, mentor , and speaker. >>…

Cooperative Interruption of a Thread in C++20: Callbacks

July 15, 2024

I introduced in my last post "Cooperative Interruption of a Thread in C++20" callbacks. Today, I dive…

TimelineCpp20Interruption

Cooperative Interruption of a Thread in C++20

July 1, 2024

/

A typical question in my C++ seminars is: Can a thread be killed? Before C++20, my answer is no. With…

My ALS Journey: 11/n

June 29, 2024

This update is a special one. I want to explain how I can still provide classes, mentoring, and presentations. >>…

Latest news

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 […]
A Lock-Free Stack: A Complete ImplementationFebruary 10, 2025 - 3:01 pm
My last lock-free stack implementation was incomplete. It only supported push operations. Let’s change this. The following paragraph about sequential consistency is optional. You can easily ignore it. Sequential Consistency In my examples, I use the default memory ordering: sequential consistency. The reason is simple. Sequential consistency provides the strongest guarantees of all memory ordering […]
My Next Mentoring Program: “Generic Programming (Templates) with C++” startsFebruary 4, 2025 - 4:51 pm
My next mentoring program, “Embedded Programming with Modern C++,” starts on January 31st. Registration is open. Here are more details. Embedded Programming with Modern C++ The mentoring program consists of 16 stations. You have to invest at least 3 hours per week for each one. This means the program takes four months, and you can […]
A Lock-Free Stack: A Simplified ImplementationFebruary 3, 2025 - 10:37 am
Today, I continue my mini story about lock-free data structures. General Considerations From the outside, the caller’s responsibility (application) is to protect the data. From inside, the data structure is responsible for protecting itself. A data structure that protects itself so a data race cannot appear is called thread-safe. First, what general considerations must you […]