Archive for year: 2018

retriever

C++ Core Guidelines: Sharing Data between Threads

May 11, 2018

/

If you want to have fun with threads, you should share mutable data between them. To get no data race…

wrench 24261 640

C++ Core Guidelines: Use Tools to Validate your Concurrent Code

May 4, 2018

/

Today, I'm happy to write about the probably most important C++ Core Guidelines for concurrency rule:…

thread 841607 640

C++ Core Guidelines: More Rules about Concurrency and Parallelism

April 27, 2018

/

Writing multithreading programs is hard, even harder if the program should be correct. The rules of the…

timeline11 14

C++ Core Guidelines: Rules for Concurrency and Parallelism

April 21, 2018

/

C++11 is the first C++ standard that deals with concurrency. The basic building block for concurrency…

RainerGrimmSmall

The new pdf bundle is ready: Functional Features in C++

April 15, 2018

/

I have prepared the pdf bundle. To get it is quite simple. If you subscribe to the newsletter, you…

cheetah

C++ Core Guidelines: The Remaining Rules about Performance

April 13, 2018

/

Today, I will write about the remaining ten rules of performance. Ten rules seem to be a lot, but only…

C++ Core Guidelines: More Rules about Performance

April 4, 2018

/

In this post, I continue my journey through the rules to performance in the C++ Core Guidelines. …

memoryFake

The Truth about “Raw Pointers Removed from C++”

April 2, 2018

/

Five bloggers have teamed up worldwide to deliver an April Fool's joke to readers about eliminating pointers.…

memory

No New New: Raw Pointers Removed from C++

March 26, 2018

/

Two weeks ago, the ISO C++ standard meeting took place in Jacksonville. Today I want to make a…

cheetah

C++ Core Guidelines: Rules about Performance

March 23, 2018

/

Before I write about the rules of performance, I will do a straightforward job. Accessing the elements…

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 […]