From: Torbjorn SVENSSON <torbjorn.svensson@foss.st.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>,
Jeff Law <jeffreyalaw@gmail.com>
Cc: Christophe Lyon <christophe.lyon@linaro.org>,
Hans-Peter Nilsson <hp@axis.com>,
gcc-patches <gcc-patches@gcc.gnu.org>,
libstdc++ <libstdc++@gcc.gnu.org>,
Jonathan Wakely <jwakely@redhat.com>,
Yvan Roux <yvan.roux@foss.st.com>
Subject: Re: Ping: [PATCH v2 1/2] testsuite: Add dg-require-atomic-cmpxchg-word
Date: Wed, 7 Feb 2024 17:31:38 +0100 [thread overview]
Message-ID: <24dada43-1606-4d5c-88b2-8e9bed07d2a7@foss.st.com> (raw)
In-Reply-To: <CAH6eHdTjAcdTvJpYs6cHTvfxXSA-jaH85zt+TRZcP0J26b6P8A@mail.gmail.com>
Hi,
Is it okay to backport 62b29347c38394ae32858f2301aa9aa65205984e,
2a4d9e4f533c77870cc0eb60fbbd8047da4c7386 and
ba0cde8ba2d93b7193050eb5ef3cc6f7a2cdfe61 to releases/gcc-13?
Without this backport, I see these failures on arm-none-eabi:
FAIL: 29_atomics/atomic/compare_exchange_padding.cc (test for excess errors)
FAIL: 29_atomics/atomic_ref/compare_exchange_padding.cc (test for excess
errors)
Kind regards,
Torbjörn
On 2023-10-13 00:23, Jonathan Wakely wrote:
>
>
> On Thu, 12 Oct 2023, 17:11 Jeff Law, <jeffreyalaw@gmail.com
> <mailto:jeffreyalaw@gmail.com>> wrote:
>
>
>
> On 10/12/23 08:38, Christophe Lyon wrote:
> > LGTM but I'm not a maintainer ;-)
> LGTM to as well -- I usually try to stay out of libstdc++, but this
> looks simple enough. Both patches in this series are OK.
>
>
> Thanks for stepping in, Jeff. The patches are indeed fine, I'm just
> offline due to circumstances beyond my control. I hope normal service
> will resume soon.
>
>
next prev parent reply other threads:[~2024-02-07 16:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 14:34 [PATCH] __atomic_test_and_set: Fall back to library, not non-atomic code Hans-Peter Nilsson
2023-09-26 15:23 ` Jeff Law
2023-10-03 13:20 ` Christophe Lyon
2023-10-03 15:16 ` Hans-Peter Nilsson
[not found] ` <CAPS5khY5fNB+AuOJOJPT7U6SgyfnvBKc+PNE4jY9oVG7UNOTCg@mail.gmail.com>
[not found] ` <20231004004929.9F76B2042E@pchp3.se.axis.com>
2023-10-04 8:53 ` Christophe Lyon
2023-10-04 2:55 ` [PATCH 1/2] testsuite: Add dg-require-atomic-exchange " Hans-Peter Nilsson
2023-10-04 8:13 ` Jonathan Wakely
2023-10-04 3:11 ` [PATCH 2/2] testsuite: Replace many dg-require-thread-fence with dg-require-atomic-exchange Hans-Peter Nilsson
2023-10-04 8:29 ` Jonathan Wakely
2023-10-04 15:15 ` Hans-Peter Nilsson
2023-10-04 16:01 ` Jonathan Wakely
2023-10-04 17:04 ` [PATCH v2 1/2] testsuite: Add dg-require-atomic-cmpxchg-word Hans-Peter Nilsson
2023-10-12 2:21 ` Ping: " Hans-Peter Nilsson
2023-10-12 14:38 ` Christophe Lyon
2023-10-12 16:10 ` Jeff Law
2023-10-12 22:23 ` Jonathan Wakely
2024-02-07 16:31 ` Torbjorn SVENSSON [this message]
2024-02-07 16:33 ` Jonathan Wakely
2024-02-07 17:37 ` Torbjorn SVENSSON
2023-10-04 17:08 ` [PATCH v2 2/2] testsuite: Replace many dg-require-thread-fence with dg-require-atomic-cmpxchg-word Hans-Peter Nilsson
2023-10-12 2:22 ` Ping: " Hans-Peter Nilsson
2023-10-12 14:40 ` Christophe Lyon
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=24dada43-1606-4d5c-88b2-8e9bed07d2a7@foss.st.com \
--to=torbjorn.svensson@foss.st.com \
--cc=christophe.lyon@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=hp@axis.com \
--cc=jeffreyalaw@gmail.com \
--cc=jwakely.gcc@gmail.com \
--cc=jwakely@redhat.com \
--cc=libstdc++@gcc.gnu.org \
--cc=yvan.roux@foss.st.com \
/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).