public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/98034] New: std::atomic_signed_lock_free and std::atomic_unsigned_lock_free not defined Date: Fri, 27 Nov 2020 13:48:17 +0000 [thread overview] Message-ID: <bug-98034-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98034 Bug ID: 98034 Summary: std::atomic_signed_lock_free and std::atomic_unsigned_lock_free not defined Product: gcc Version: 11.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: redi at gcc dot gnu.org CC: rodgertq at gcc dot gnu.org Target Milestone: --- C++20 adds these typedefs. For linux they should be atomic<int> and atomic<unsigned>, because they can use futex for waiting and notifying. I don't know about other targets.
next reply other threads:[~2020-11-27 13:48 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-27 13:48 redi at gcc dot gnu.org [this message] 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 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@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).