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++/98034] std::atomic_signed_lock_free and std::atomic_unsigned_lock_free not defined Date: Mon, 12 Dec 2022 14:00:56 +0000 [thread overview] Message-ID: <bug-98034-4-sYt8YHZipG@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98034-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98034 --- Comment #3 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>: https://gcc.gnu.org/g:320ac807da125e6dc952b3d4abf02daeead88d44 commit r13-4612-g320ac807da125e6dc952b3d4abf02daeead88d44 Author: Jonathan Wakely <jwakely@redhat.com> Date: Mon Dec 12 12:49:40 2022 +0000 libstdc++: Define atomic lock-free type aliases for C++20 [PR98034] libstdc++-v3/ChangeLog: PR libstdc++/98034 * include/std/atomic (__cpp_lib_atomic_lock_free_type_aliases): Define macro. (atomic_signed_lock_free, atomic_unsigned_lock_free): Define aliases. * include/std/version (__cpp_lib_atomic_lock_free_type_aliases): Define macro. * testsuite/29_atomics/atomic/lock_free_aliases.cc: New test.
next prev parent reply other threads:[~2022-12-12 14:00 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-27 13:48 [Bug libstdc++/98034] New: " redi at gcc dot gnu.org 2020-11-27 13:49 ` [Bug libstdc++/98034] " redi at gcc dot gnu.org 2020-11-30 19:27 ` rodgertq at gcc dot gnu.org 2021-02-01 16:01 ` redi at gcc dot gnu.org 2022-12-12 14:00 ` cvs-commit at gcc dot gnu.org [this message] 2022-12-12 14:04 ` redi 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-98034-4-sYt8YHZipG@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).