From: Jeff Law <jeffreyalaw@gmail.com>
To: Hans-Peter Nilsson <hp@axis.com>,
gcc-patches@gcc.gnu.org, libstdc++@gcc.gnu.org
Subject: Re: [PATCH] testsuite: Require thread-fence for 29_atomics/atomic_flag/cons/value_init.cc
Date: Tue, 26 Sep 2023 09:20:51 -0600 [thread overview]
Message-ID: <177b0259-e643-4f25-9a7f-705652fb8d78@gmail.com> (raw)
In-Reply-To: <20230926144058.874C82042E@pchp3.se.axis.com>
On 9/26/23 08:40, Hans-Peter Nilsson wrote:
> Ok to commit?
> -- >8 --
> A recent patch made __atomic_test_and_set no longer fall
> back to emitting non-atomic code, but instead will then emit
> a call to __atomic_test_and_set, thereby exposing the need
> to gate also this test on support for atomics, similar to
> r14-3980-g62b29347c38394.
>
> libstdc++-v3:
> * testsuite/29_atomics/atomic_flag/cons/value_init.cc: Add
> dg-require-thread-fence.
OK.
Jeff
ps. Missed you at the Cauldron....
prev parent reply other threads:[~2023-09-26 15:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 14:40 Hans-Peter Nilsson
2023-09-26 15:20 ` Jeff Law [this message]
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=177b0259-e643-4f25-9a7f-705652fb8d78@gmail.com \
--to=jeffreyalaw@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hp@axis.com \
--cc=libstdc++@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).