CppMem

Ongoing Optimization: Relaxed Semantic with CppMem

With the relaxed semantic, we have no synchronisations and ordering constraints on atomic operations.

Read more
Comments 2Views: 1474

Ongoing Optimization: A Data Race with CppMem

But we can do better and further improve the acquire-release semantic of the last post. Why should x be an atomic? There is no reason. That was my first, but incorrect assumption. See why?

Read more
Comments 1Views: 1416

Ongoing Optimization: Acquire-Release Semantic with CppMem

With the acquire-releae semantic, we break the sequential consistency. In the acquire-release semantic the synchronization takes place between atomic operations on the same atomic and not between threads.

Read more
Add CommentViews: 1055

Ongoing Optimization: Sequential Consistency with CppMem

With atomic data types you can tailor your program to your needs and therefore optimize it. But now we are in the domain of the multithreading experts.

Read more
Comments 4Views: 2016

Ongoing Optimization: Locks and Volatile with CppMem

The easiest way to solve the undefined behaviour in the post Ongoing Optimization: Unsynchronized access is, to use a lock.

Read more
Add CommentViews: 1517

Ongoing Optimization: Unsynchronized Access with CppMem

I've described my challenge in the last post. Let' start with our process of ongoing optimization. To be sure, I verify my reasoning with CppMem. I once made a big mistake in my presentation at Meeting C++ 2014.

Read more
Comments 2Views: 3165

Ongoing Optimization

Now it's time to put the theory into practice. The job is quite easy. A small program should undergo an ongoing optimization.

Read more
Comments 7Views: 2519

My Newest E-Book

Latest comments

Subscribe to the newsletter (+ pdf bundle)

Blog archive

Source Code

Visitors

Today 78

All 332202

Currently are 165 guests and no members online