public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Matthew Wahab <matthew.wahab@foss.arm.com>
To: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH 1/4][ARM][PR target/65697][5.1] Backport stronger barriers for __sync fetch-op builtins.
Date: Mon, 27 Jul 2015 10:31:00 -0000	[thread overview]
Message-ID: <55B60823.6070905@foss.arm.com> (raw)
In-Reply-To: <559538D3.8010302@foss.arm.com>

[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]

Ping. Updated patch attached.

Also, retested for arm-none-linux-gnueabihf with native bootstrap and make
check and for arm-none-eabi with cross compiled make check.

On 02/07/15 14:12, Matthew Wahab wrote:
> The __sync builtins are implemented using barriers that are too weak for ARMv8
> targets, this has been fixed on trunk for the ARM back-end. Since GCC-5.1 is
> also generating the incorrect code, it should also be fixed.
>
> This patch backports the changes made to strengthen the barriers emitted for
> the __sync fetch-and-op/op-and-fetch builtins.
>
> The trunk patch submission is at
> https://gcc.gnu.org/ml/gcc-patches/2015-06/msg01410.html
> The commit is at https://gcc.gnu.org/ml/gcc-cvs/2015-06/msg01235.html
>
> Tested the series for arm-none-linux-gnueabihf with check-gcc
>
> Ok for the branch?
> Matthew
>
> 2015-07-02  Matthew Wahab  <matthew.wahab@arm.com>
>
>      Backport from trunk:
>      2015-06-29  Matthew Wahab  <matthew.wahab@arm.com>
>
>      PR target/65697
>      * config/armc/arm.c (arm_split_atomic_op): For ARMv8, replace an
>      initial acquire barrier with final barrier.


[-- Attachment #2: 0001-2015-07-01-Matthew-Wahab-matthew.wahab-arm.com.patch --]
[-- Type: text/x-patch, Size: 2082 bytes --]

From 0c2f209f869aead3475fe491f08cf7640d2bc8fe Mon Sep 17 00:00:00 2001
From: mwahab <mwahab@138bc75d-0d04-0410-961f-82ee72b054a4>
Date: Mon, 29 Jun 2015 16:03:34 +0000
Subject: [PATCH 1/4] 2015-07-01  Matthew Wahab  <matthew.wahab@arm.com>

        Backport
	PR target/65697
	* config/armc/arm.c (arm_split_atomic_op): For ARMv8, replace an
	initial acquire barrier with final barrier.

git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@225132 138bc75d-0d04-0410-961f-82ee72b054a4

Conflicts:
	gcc/ChangeLog

Change-Id: I2074541794ecad8847ada04690cd9132a51b6404
---
 gcc/config/arm/arm.c | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/gcc/config/arm/arm.c b/gcc/config/arm/arm.c
index 614ff0d..f694e74 100644
--- a/gcc/config/arm/arm.c
+++ b/gcc/config/arm/arm.c
@@ -27822,6 +27822,8 @@ arm_split_atomic_op (enum rtx_code code, rtx old_out, rtx new_out, rtx mem,
   rtx_code_label *label;
   rtx x;
 
+  bool is_armv8_sync = arm_arch8 && is_mm_sync (model);
+
   bool use_acquire = TARGET_HAVE_LDACQ
                      && !(is_mm_relaxed (model) || is_mm_consume (model)
 			  || is_mm_release (model));
@@ -27830,6 +27832,11 @@ arm_split_atomic_op (enum rtx_code code, rtx old_out, rtx new_out, rtx mem,
                      && !(is_mm_relaxed (model) || is_mm_consume (model)
 			  || is_mm_acquire (model));
 
+  /* For ARMv8, a load-acquire is too weak for __sync memory orders.  Instead,
+     a full barrier is emitted after the store-release.  */
+  if (is_armv8_sync)
+    use_acquire = false;
+
   /* Checks whether a barrier is needed and emits one accordingly.  */
   if (!(use_acquire || use_release))
     arm_pre_atomic_barrier (model);
@@ -27900,7 +27907,8 @@ arm_split_atomic_op (enum rtx_code code, rtx old_out, rtx new_out, rtx mem,
   emit_unlikely_jump (gen_cbranchsi4 (x, cond, const0_rtx, label));
 
   /* Checks whether a barrier is needed and emits one accordingly.  */
-  if (!(use_acquire || use_release))
+  if (is_armv8_sync
+      || !(use_acquire || use_release))
     arm_post_atomic_barrier (model);
 }
 \f
-- 
1.9.1


  parent reply	other threads:[~2015-07-27 10:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-02 13:12 Matthew Wahab
2015-07-02 13:15 ` [PATCH 2/4][ARM][PR target/65697][5.1] Backport stronger barriers for __sync,compare-and-swap builtins Matthew Wahab
2015-07-27 10:32   ` Matthew Wahab
2015-07-31  9:41     ` Ramana Radhakrishnan
2015-07-02 13:17 ` [PATCH 3/4][ARM][PR target/65697][5.1] Add tests for __sync_builtins Matthew Wahab
2015-07-27 10:32   ` Matthew Wahab
2015-07-31  9:41     ` Ramana Radhakrishnan
2015-07-02 13:18 ` [PATCH 4/4][ARM][PR target/65697][5.1] Fix " Matthew Wahab
2015-07-27 10:43   ` Matthew Wahab
2015-07-31  9:49     ` Ramana Radhakrishnan
2015-07-27 10:31 ` Matthew Wahab [this message]
2015-07-31  9:39   ` [PATCH 1/4][ARM][PR target/65697][5.1] Backport stronger barriers for __sync fetch-op builtins Ramana Radhakrishnan

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=55B60823.6070905@foss.arm.com \
    --to=matthew.wahab@foss.arm.com \
    --cc=gcc-patches@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).