惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

The GitHub Blog
The GitHub Blog
Engineering at Meta
Engineering at Meta
博客园 - 聂微东
博客园 - Franky
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
雷峰网
雷峰网
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
L
LangChain Blog
WordPress大学
WordPress大学
H
Help Net Security
H
Hackread – Cybersecurity News, Data Breaches, AI and More
Y
Y Combinator Blog
Blog — PlanetScale
Blog — PlanetScale
MyScale Blog
MyScale Blog
IT之家
IT之家
酷 壳 – CoolShell
酷 壳 – CoolShell
罗磊的独立博客
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
有赞技术团队
有赞技术团队
Apple Machine Learning Research
Apple Machine Learning Research
云风的 BLOG
云风的 BLOG
博客园 - 【当耐特】
P
Proofpoint News Feed
D
DataBreaches.Net

Lei Mao's Log Book

2026 FIFA World Cup 备受嘲讽的会徽 Python Debugging Via VS Code In Docker Container Vargas Plateau Regional Park 徒步 Vargas Plateau Regional Park Apex 2026 FIFA World Cup 小组赛赛程 Retaining EXIF Metadata In GIMP San Francisquito Creek Joint Powers Authority 2025 Calendar Photo 麦当劳 The FIFA World Cup 套餐 Ardenwood Historic Farm 徒步 Ardenwood Historic Farm Synchronizations With TorchRec KeyedJaggedTensor Pacific Commons Linear Park 徒步 Pacific Commons Linear Park 2026 San Jose Half Marathon 竞赛 目标 Mountain View Shoreline Park 徒步 Mountain View Shoreline Park PyTorch AOTInductor Hybrid Lowering Carquinez Strait Regional Shoreline 徒步 Carquinez Strait Regional Shoreline PyTorch Triton Kernel Transparent Tracing and Compilation 脸庞 PyTorch Fake Export 2026 BRAIN Foundation 10K 竞赛 2026 Wild and Scenic Film Festival 参观 2026 Wild and Scenic Film Festival 系统工程程序员修 Bug FIFA 官方网站的语言 PyTorch Custom Operation
C++ Latch and Barrier
2026-02-06 · via Lei Mao's Log Book

Introduction

Scheduling threads and synchronizing their execution is a common requirement in concurrent programming. In C++11, the std::condition_variable was introduced to facilitate thread synchronization. However, creating such mechanisms can be complex and error-prone. In C++20, two new synchronization primitives, std::latch and std::barrier, were introduced to simplify thread synchronization in certain scenarios.

In this blog post, I would like to demonstrate how to use create new implementations using std::latch and std::barrier to replace an existing producer-consumer model example implementation using std::condition_variable.

C++ Condition Variable

In my previous blog post “C++ Condition Variable”, I demonstrated how to use std::condition_variable introduced in C++11 to synchronize threads using the following producer-consumer model example.

wait_notify.cpp
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
#include <chrono>
#include <condition_variable>
#include <iostream>
#include <mutex>
#include <string>
#include <thread>

std::mutex m;
std::condition_variable cv;
std::string data;
bool ready = false;
bool processed = false;

void worker_thread()
{
std::cout << "Worker thread start" << std::endl;
std::unique_lock<std::mutex> lk(m);
cv.wait(lk, [] { return ready; });


std::cout << "Worker thread is processing data" << std::endl;
data += " after processing";


processed = true;
std::cout << "Worker thread signals data processing completed" << std::endl;



lk.unlock();


cv.notify_one();
}

void master_thread()
{
std::cout << "Master thread start" << std::endl;
data = "Example data";

{
std::lock_guard<std::mutex> lk(m);
ready = true;
std::cout << "Master thread signals data ready for processing"
<< std::endl;
}


cv.notify_one();


{
std::unique_lock<std::mutex> lk(m);
cv.wait(lk, [] { return processed; });
}
std::cout << "Back in master thread, data = " << data << std::endl;
}

int main()
{
std::thread worker(worker_thread), master(master_thread);


worker.join();
master.join();
}
1
2
3
4
5
6
7
8
$ g++ wait_notify.cpp -o wait_notify -std=c++11
$ ./wait_notify
Worker thread start
Master thread start
Master thread signals data ready for processing
Worker thread is processing data
Worker thread signals data processing completed
Back in master thread, data = Example data after processing

C++ Latch and Barrier

The above example works fine, but it requires careful management of mutexes, condition variables, and spurious wakeups, which is somewhat tedious and confusing. The same producer-consumer model example can be implemented more straightforwardly using the new synchronization primitives std::latch or std::barrier introduced in C++20.

The key difference between std::latch and std::barrier is that a latch is a one-time-use synchronization primitive, while a barrier can be reused multiple times. A latch is typically used when you want to wait for a set of threads to complete their tasks before proceeding, whereas a barrier is used when you want to synchronize a set of threads at multiple points in their execution.

C++ Latch

Compared to the implementation using std::condition_variable, the implementation using std::latch is much simpler and easier to understand.

latch.cpp
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
#include <chrono>
#include <iostream>
#include <latch>
#include <string>
#include <thread>

std::string data;
std::latch worker_latch(1);
std::latch master_latch(1);

void worker_thread()
{
std::cout << "Worker thread start" << std::endl;

worker_latch.wait();


std::cout << "Worker thread is processing data" << std::endl;
data += " after processing";


std::cout << "Worker thread signals data processing completed" << std::endl;
master_latch.count_down();
}

void master_thread()
{
std::cout << "Master thread start" << std::endl;
data = "Example data";

std::cout << "Master thread signals data ready for processing"
<< std::endl;
worker_latch.count_down();


master_latch.wait();
std::cout << "Back in master thread, data = " << data << std::endl;
}

int main()
{
std::thread worker(worker_thread), master(master_thread);


worker.join();
master.join();
}
1
2
3
4
5
6
7
8
$ g++ latch.cpp -o latch -std=c++20
$ ./latch
Worker thread start
Master thread start
Master thread signals data ready for processing
Worker thread is processing data
Worker thread signals data processing completed
Back in master thread, data = Example data after processing

C++ Barrier

Similarly, the same example could be implemented using std::barrier. Note that in this case, instead of using two latches, we can reuse a single barrier for synchronization between the master and worker threads.

barrier.cpp
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
#include <barrier>
#include <chrono>
#include <iostream>
#include <string>
#include <thread>

std::string data;
std::barrier sync_point(2);

void worker_thread()
{
std::cout << "Worker thread start" << std::endl;

sync_point.arrive_and_wait();


std::cout << "Worker thread is processing data" << std::endl;
data += " after processing";


std::cout << "Worker thread signals data processing completed" << std::endl;
sync_point.arrive_and_wait();
}

void master_thread()
{
std::cout << "Master thread start" << std::endl;
data = "Example data";

std::cout << "Master thread signals data ready for processing"
<< std::endl;
sync_point.arrive_and_wait();


sync_point.arrive_and_wait();
std::cout << "Back in master thread, data = " << data << std::endl;
}

int main()
{
std::thread worker(worker_thread), master(master_thread);


worker.join();
master.join();
}
1
2
3
4
5
6
7
8
$ g++ barrier.cpp -o barrier -std=c++20
$ ./barrier
Worker thread start
Master thread start
Master thread signals data ready for processing
Worker thread is processing data
Worker thread signals data processing completed
Back in master thread, data = Example data after processing

Conclusions

The std::latch and std::barrier synchronization primitives introduced in C++20 are important concepts for thread synchronization especially used in producer-consumer models. They provide a simpler and more intuitive way to manage thread synchronization compared to traditional methods using mutexes and condition variables.

References