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: 6757

CppMem - An Overview

CppMem is an interactive tool for exploring the behaviour of small code snippets of the C++ memory model. It should, no it has to be in the tool box of each programmer, who deals seriously with the memory model.

Read more
Comments 27Views: 12902

Relaxed Semantic

The relaxed semantic is the end of the Scala. The relaxed semantic is the weakest of all memory models and guarantees only, that the operations on atomic variables are atomic.

Read more
Comments 11Views: 10494

Acquire-Release Fences

Acquire and release fences guarantees similar synchronisation and ordering constraints as atomics with acquire-release semantic. Similar, because the differences are in the details.

Read more
Comments 11Views: 15121

Fences are Memory Barriers

The key idea of a std::atomic_thread_fence is, to establish synchronisation and ordering constraints between threads without an atomic operation.

Read more
Comments 8Views: 30772

Acquire-Release Semantic - The typical Misunderstanding

A release operation synchronizes-with an acquire operation on the same atomic variable. So we can easily synchronise threads, if ... . Today's post is about the if.

Read more
Comments 2Views: 11038

memory_order_consume

std::memory_order_consume is the most legendary of the six memory models. That's for two reasons. At one hand, std::memory_order_consume is extremely hard to get. At the other hand - that may change in the future - no compiler supports it.

Read more
Comments 3Views: 11063

100 Posts Anniversary - Quo vadis Modernes C++?

As you may know, I translate in this blog the posts from my German blog into English. My German blog has the 100 posts anniversary. So I started a poll for the next new main topic.

Read more
Comments 4Views: 7124

Transitivity of the Acquire-Release Semantic

A release operation synchronises with an acquire operation on the same atomic variable and establishes, in addition, an ordering constraints. These are the components to synchronise threads in a performant way, in case they act on the same atomic. But how can that work, if two threads share no atomic variable? We want no sequential consistency because that is too heavy. We want the light acquire-release semantic.

Read more
Add CommentViews: 5373

Subscribe to the newsletter (+ pdf bundle)

Blog archive

Source Code

Visitors

Today 2235

All 2177423

Currently are 141 guests and no members online

Kubik-Rubik Joomla! Extensions

Latest comments