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++/114103] FAIL: 29_atomics/atomic/lock_free_aliases.cc  -std=gnu++20 (test for excess errors)
Date: Thu, 07 Mar 2024 21:00:17 +0000	[thread overview]
Message-ID: <bug-114103-4-xMpuZ3Dynk@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114103-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #16 from GCC 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:e162b2ff52c5e20f6624ff6b66845fe573cef183

commit r14-9371-ge162b2ff52c5e20f6624ff6b66845fe573cef183
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Mon Feb 26 13:17:32 2024 +0000

    libstdc++: Do not define lock-free atomic aliases if not fully lock-free
[PR114103]

    The whole point of these typedefs is to guarantee lock-freedom, so if
    the target has no such types, we shouldn't defined the typedefs at all.

    libstdc++-v3/ChangeLog:

            PR libstdc++/114103
            * include/bits/version.def (atomic_lock_free_type_aliases): Add
            extra_cond to check for at least one always-lock-free type.
            * include/bits/version.h: Regenerate.
            * include/std/atomic (atomic_signed_lock_free)
            (atomic_unsigned_lock_free): Only use always-lock-free types.
            * src/c++20/tzdb.cc (time_zone::_Impl::RulesCounter): Don't use
            atomic counter if lock-free aliases aren't available.
            * testsuite/29_atomics/atomic/lock_free_aliases.cc: XFAIL for
            targets without lock-free word-size compare_exchange.

  parent reply	other threads:[~2024-03-07 21:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-25 17:47 [Bug libstdc++/114103] New: " danglin at gcc dot gnu.org
2024-02-26 10:54 ` [Bug libstdc++/114103] " redi at gcc dot gnu.org
2024-02-26 10:55 ` redi at gcc dot gnu.org
2024-02-26 10:56 ` redi at gcc dot gnu.org
2024-02-26 12:21 ` dave.anglin at bell dot net
2024-02-26 12:22 ` redi at gcc dot gnu.org
2024-02-26 12:25 ` dave.anglin at bell dot net
2024-02-27 14:32 ` redi at gcc dot gnu.org
2024-02-27 20:49 ` dave.anglin at bell dot net
2024-02-28  1:04 ` dave.anglin at bell dot net
2024-02-28  9:31 ` redi at gcc dot gnu.org
2024-02-29 17:44 ` redi at gcc dot gnu.org
2024-03-01 22:15 ` dave.anglin at bell dot net
2024-03-01 22:35 ` redi at gcc dot gnu.org
2024-03-01 22:38 ` redi at gcc dot gnu.org
2024-03-01 22:42 ` redi at gcc dot gnu.org
2024-03-02 23:36 ` dave.anglin at bell dot net
2024-03-07 21:00 ` cvs-commit at gcc dot gnu.org [this message]
2024-03-07 21:01 ` redi at gcc dot gnu.org
2024-03-23 18:12 ` danglin 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-114103-4-xMpuZ3Dynk@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: link
Be 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).