diff options
| author | Jonathan Wakely <jwakely@redhat.com> | 2024-11-13 12:57:11 +0000 |
|---|---|---|
| committer | Jonathan Wakely <redi@gcc.gnu.org> | 2024-11-13 17:58:49 +0000 |
| commit | 42def7cd8bab71002d3097b9db33fd1dc25a72f6 (patch) | |
| tree | 1058912a7af31d0620f94a173e14f9202532a9b5 /gcc | |
| parent | 2d7d8179cbccaddb308c966b9c1d4840c0d56b03 (diff) | |
| download | gcc-42def7cd8bab71002d3097b9db33fd1dc25a72f6.zip gcc-42def7cd8bab71002d3097b9db33fd1dc25a72f6.tar.gz gcc-42def7cd8bab71002d3097b9db33fd1dc25a72f6.tar.bz2 | |
libstdc++: Fix nodiscard warnings in perf test for memory pools
The use of unnamed std::lock_guard temporaries was intentional here, as
they were used like barriers (but std::barrier isn't available until
C++20). But that gives nodiscard warnings, because unnamed temporary
locks are usually unintentional. Use named variables in new block scopes
instead.
libstdc++-v3/ChangeLog:
* testsuite/performance/20_util/memory_resource/pools.cc: Fix
-Wunused-value warnings about unnamed std::lock_guard objects.
Diffstat (limited to 'gcc')
0 files changed, 0 insertions, 0 deletions