public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/98034] New: std::atomic_signed_lock_free and std::atomic_unsigned_lock_free not defined
@ 2020-11-27 13:48 redi at gcc dot gnu.org
  2020-11-27 13:49 ` [Bug libstdc++/98034] " redi at gcc dot gnu.org
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: redi at gcc dot gnu.org @ 2020-11-27 13:48 UTC (permalink / raw)
  To: gcc-bugs

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.

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2022-12-12 14:04 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-11-27 13:48 [Bug libstdc++/98034] New: std::atomic_signed_lock_free and std::atomic_unsigned_lock_free not defined 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
2022-12-12 14:04 ` redi at gcc dot gnu.org

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).