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

* [Bug libstdc++/98034] std::atomic_signed_lock_free and std::atomic_unsigned_lock_free not defined
  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 ` redi at gcc dot gnu.org
  2020-11-30 19:27 ` rodgertq at gcc dot gnu.org
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: redi at gcc dot gnu.org @ 2020-11-27 13:49 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98034

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Also, we should probably be using a futex directly for unsigned, and for other
types with the same size and alignment as int (e.g. long on ilp32 targets).

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

* [Bug libstdc++/98034] std::atomic_signed_lock_free and std::atomic_unsigned_lock_free not defined
  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
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: rodgertq at gcc dot gnu.org @ 2020-11-30 19:27 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98034

Thomas Rodgers <rodgertq at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |ASSIGNED
   Last reconfirmed|                            |2020-11-30

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

* [Bug libstdc++/98034] std::atomic_signed_lock_free and std::atomic_unsigned_lock_free not defined
  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
  4 siblings, 0 replies; 6+ messages in thread
From: redi at gcc dot gnu.org @ 2021-02-01 16:01 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98034

--- Comment #2 from Jonathan Wakely <redi at gcc dot gnu.org> ---
(In reply to Jonathan Wakely from comment #0)
> C++20 adds these typedefs.

And the __cpp_lib_atomic_lock_free_type_aliases feature test macro.

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

* [Bug libstdc++/98034] std::atomic_signed_lock_free and std::atomic_unsigned_lock_free not defined
  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
                   ` (2 preceding siblings ...)
  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
  4 siblings, 0 replies; 6+ messages in thread
From: cvs-commit at gcc dot gnu.org @ 2022-12-12 14:00 UTC (permalink / raw)
  To: gcc-bugs

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.

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

* [Bug libstdc++/98034] std::atomic_signed_lock_free and std::atomic_unsigned_lock_free not defined
  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
                   ` (3 preceding siblings ...)
  2022-12-12 14:00 ` cvs-commit at gcc dot gnu.org
@ 2022-12-12 14:04 ` redi at gcc dot gnu.org
  4 siblings, 0 replies; 6+ messages in thread
From: redi at gcc dot gnu.org @ 2022-12-12 14:04 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98034

Jonathan Wakely <redi at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|ASSIGNED                    |RESOLVED

--- Comment #4 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Implemented for GCC 13

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