Now it's time to put the theory into practice. The job is quite easy. A small program should undergo an ongoing optimization.
The program
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
|
// ongoingOptimization.cpp
#include <iostream>
#include <thread>
int x= 0;
int y= 0;
void writing(){
x= 2000;
y= 11;
}
void reading(){
std::cout << "y: " << y << " ";
std::cout << "x: " << x << std::endl;
}
int main(){
std::thread thread1(writing);
std::thread thread2(reading);
thread1.join();
thread2.join();
}
|
The program is quite simple. It consists of two threads thread1 and thread2.thread1 writes the values x and y. thread 2 reads the values x and y in the opposite direction. The execution of the program is not so thrilling either.

But you see, even this simple program has different results. So I finally come to my key idea.
In the process of ongoing optimization of the program I have two questions in my mind.
- Is the program well defined? Precisely, is there a data race?
- Which values for x and y are possible?
The first question is often very challenging to answer. So I will reason in the first step about the program and I will verify in the second step my reasoning with CppMem. If I have answered the first question, the second answer can easily be derived. I will provide the possible values in a table.

But still, one question isn't answered yet? What do I mean by ongoing optimization? I mean by ongoing optimization, that I try to improve the program by weakening the C++ memory model. So in my journey I discuss the following stations.
- Non atomic variables
- Locks
- Atomics with sequential consistency
- Atomics with acquire-release semantic
- Atomics with relaxed semantic
- Volatile variables
What's next?
Of course, this was a very short post. But this post should provide you only the context of my ongoing optimization. In case you are bored, reason about the small program and answer the two question.
- Is the program well defined?
- Which values for x and y are possible?
Still bored? Then reason about the weakening of the memory model in the program and about the consequences. In the next post, I will analyse the unsynchronized access with the help of CppMem. Stay tuned.
Thanks a lot to my Patreon Supporters: Matt Braun, Roman Postanciuc, Tobias Zindl, Marko, G Prvulovic, Reinhold Dröge, Abernitzke, Frank Grimm, Sakib, Broeserl, António Pina, Darshan Mody, Sergey Agafyin, Андрей Бурмистров, Jake, GS, Lawton Shoemake, Animus24, Jozo Leko, John Breland, espkk, Wolfgang Gärtner, Louis St-Amour, Stephan Roslen, Venkat Nandam, Jose Francisco, Douglas Tinkham, Kuchlong Kuchlong, Avi Kohn, Robert Blanch, Truels Wissneth, Kris Kafka, Mario Luoni, Neil Wang, Friedrich Huber, lennonli, Pramod Tikare Muralidhara, Peter Ware, and Tobi Heideman.
Thanks in particular to Jon Hess, Lakshman, Christian Wittenhorst, Sherhy Pyton, Dendi Suhubdy, Sudhakar Belagurusamy, and Richard Sargeant.
My special thanks to Embarcadero 
Seminars
I'm happy to give online-seminars or face-to-face seminars world-wide. Please call me if you have any questions.
Bookable (Online)
Deutsch
English
Standard Seminars
Here is a compilation of my standard seminars. These seminars are only meant to give you a first orientation.
New
Contact Me
Modernes C++,

Comments
all the great posts.
gossips and internet and this is actually frustrating.
A good web site with interesting content, that is what I need.
Thank you for keeping this web site, I will be visiting it.
Do you do newsletters? Cant find it.
for the post on this perfect one :D.
site, I'd rate it 10 10.
by mistake, while I was looking on Aol for something else, Anyways I am here now and would just like to say
thank you for a incredible post and a all round exciting blog (I
also love the theme/design), I don't have time to go through it all at the moment but I have book-marked it
and also included your RSS feeds, so when I have time I will be back to read
much more, Please do keep up the superb
job.
RSS feed for comments to this post