public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/103934] std::atomic_flag: multiple C++20 functions missing Date: Tue, 14 Feb 2023 01:47:24 +0000 [thread overview] Message-ID: <bug-103934-4-kWULT0MqAb@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-103934-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103934 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Thomas Rodgers <rodgertq@gcc.gnu.org>: https://gcc.gnu.org/g:a8d769045b43e8509490362865a85cb31a855ccf commit r13-5976-ga8d769045b43e8509490362865a85cb31a855ccf Author: Thomas W Rodgers <rodgert@twrodgers.com> Date: Fri Feb 10 09:35:11 2023 -0800 libstdc++: Add missing free functions for atomic_flag [PR103934] This patch adds - atomic_flag_test atomic_flag_test_explicit Which were missed when commit 491ba6 introduced C++20 atomic flag test. libstdc++-v3/ChangeLog: PR libstdc++/103934 * include/std/atomic (atomic_flag_test): Add. (atomic_flag_test_explicit): Add. * testsuite/29_atomics/atomic_flag/test/explicit.cc: Add test case to cover missing atomic_flag free functions. * testsuite/29_atomics/atomic_flag/test/implicit.cc: Likewise.
next prev parent reply other threads:[~2023-02-14 1:47 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-06 22:01 [Bug libstdc++/103934] New: " gcc_bugzilla at axeitado dot com 2022-02-02 21:45 ` [Bug libstdc++/103934] " redi at gcc dot gnu.org 2023-02-03 11:08 ` redi at gcc dot gnu.org 2023-02-14 1:47 ` cvs-commit at gcc dot gnu.org [this message] 2023-02-14 1:47 ` cvs-commit at gcc dot gnu.org 2023-02-14 1:59 ` cvs-commit at gcc dot gnu.org 2023-02-14 2:00 ` cvs-commit at gcc dot gnu.org 2023-03-10 2:18 ` cvs-commit at gcc dot gnu.org 2023-03-10 2:36 ` cvs-commit at gcc dot gnu.org 2023-03-10 2:43 ` rodgertq at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-103934-4-kWULT0MqAb@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).