From: Richard Sandiford <richard.sandiford@arm.com>
To: "Pop\, Sebastian" <spop@amazon.com>
Cc: Wilco Dijkstra <Wilco.Dijkstra@arm.com>, "Pop\,
Sebastian via Gcc-patches" <gcc-patches@gcc.gnu.org>
Subject: Re: [AArch64] PR105162: emit barrier for __sync and __atomic builtins on CPUs without LSE
Date: Mon, 16 May 2022 12:42:31 +0100 [thread overview]
Message-ID: <mpttu9pzot4.fsf@arm.com> (raw)
In-Reply-To: <1652473945537.58446@amazon.com> (Sebastian Pop's message of "Fri, 13 May 2022 20:32:25 +0000")
"Pop, Sebastian" <spop@amazon.com> writes:
> Please see attached the patch back-ported to branches 12, 11, 10, and 9.
> Tested on aarch64-linux with bootstrap and regression test.
> Ok to commit to the GCC active branches?
OK, thanks. Only very safe patches are supposed to be going into GCC 9
at this stage, and I guess this one is a bit on the edge. But I think
it's worth applying anyway because it's fixing a non-determinstic
wrong-code regression.
Richard
prev parent reply other threads:[~2022-05-16 11:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-07 20:15 Pop, Sebastian
2022-04-18 18:22 ` Pop, Sebastian
2022-04-19 12:51 ` Wilco Dijkstra
2022-04-25 22:06 ` Pop, Sebastian
2022-05-03 15:33 ` Wilco Dijkstra
2022-05-04 14:23 ` Pop, Sebastian
2022-05-13 14:58 ` Richard Sandiford
2022-05-13 15:41 ` Wilco Dijkstra
2022-05-13 20:32 ` Pop, Sebastian
2022-05-16 11:42 ` Richard Sandiford [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=mpttu9pzot4.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=spop@amazon.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).