From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <libc-ports-return-4313-listarch-libc-ports=sources.redhat.com@sourceware.org>
Received: (qmail 32099 invoked by alias); 19 Aug 2013 19:21:14 -0000
Mailing-List: contact libc-ports-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <libc-ports.sourceware.org>
List-Subscribe: <mailto:libc-ports-subscribe@sourceware.org>
List-Post: <mailto:libc-ports@sourceware.org>
List-Help: <mailto:libc-ports-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: libc-ports-owner@sourceware.org
Received: (qmail 32088 invoked by uid 89); 19 Aug 2013 19:21:13 -0000
X-Spam-SWARE-Status: No, score=-4.1 required=5.0 tests=BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,SPF_PASS autolearn=ham version=3.3.2
Received: from mail-wi0-f175.google.com (HELO mail-wi0-f175.google.com) (209.85.212.175)    by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Mon, 19 Aug 2013 19:21:13 +0000
Received: by mail-wi0-f175.google.com with SMTP id hq12so3492859wib.2        for <libc-ports@sourceware.org>; Mon, 19 Aug 2013 12:21:11 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=google.com; s=20120113;        h=x-gm-message-state:mime-version:in-reply-to:references:date         :message-id:subject:from:to:cc:content-type;        bh=jv1eODNpSMEXrq9EPnx9QuUhSp/NTcyF/uSGj6WwoC0=;        b=DZ7m2Fgh8X0xpZA8fcYOYUVuknBA69S8DK8w4NZD+SbJegDk3D/CwZV87ppi7HL3bC         CEm86SkuCk4tsjiiQKrW72nJ06KUrBVZEoCj6pfVg2cK1ccky/Y8q+fk+65QxbwX2Ir5         Kdhhr9+DYkdYuVF/J/Wu4At4vTdAr2aDVXyE7HCOf+JKt/sTVQdvFJ8Wmubniin1UcsN         v835vW+Aer+qnjELrRIbl8l4wMG6rO8BtRfWgjbTYKS1h9ImNofge7btCpQuXC/99+xL         m/2HiTWevfG0vhzmpZ66wjkujp6WZzqGFjJcS0DgUCsRPZX47camWtGgO0bjCAtXZYpn         pmhw==
X-Gm-Message-State: ALoCoQn3e4htsRDaO1ZNvuaYbhfE0YqV6mdf0m8aiyc3vsXw2vaw+gc3NBYVCd9/6EvD9k9uFWOe
MIME-Version: 1.0
X-Received: by 10.180.109.167 with SMTP id ht7mr9449193wib.45.1376940071010; Mon, 19 Aug 2013 12:21:11 -0700 (PDT)
Received: by 10.194.238.72 with HTTP; Mon, 19 Aug 2013 12:21:10 -0700 (PDT)
In-Reply-To: <0E42B6C0C4628E48B8DF5D3F3C8FCA8898F288A272@HQMAIL02.nvidia.com>
References: <CANoaTN2hKTZ7GZCMsYqai25PHO7GLb56huLosR7+dgjAEK2FGQ@mail.gmail.com>	<0E42B6C0C4628E48B8DF5D3F3C8FCA8898F1F8BF56@HQMAIL02.nvidia.com>	<CANoaTN0MFzWmG8e7cuWkw067qp_p_UgsABtBXCcY+8CZRADzeg@mail.gmail.com>	<0E42B6C0C4628E48B8DF5D3F3C8FCA8898F288A272@HQMAIL02.nvidia.com>
Date: Mon, 19 Aug 2013 19:21:00 -0000
Message-ID: <CANoaTN0+LngcY-RH7g3T_3fSg1XOrHov0jfRFpTe_+O99PvJqQ@mail.gmail.com>
Subject: Re: [Patch] ARM define atomic_exchange_acq/atomic_exchange_rel to __atomic_exchange_n
From: Dinar Temirbulatov <dinar@kugelworks.com>
To: Abhishek Deb <adeb@nvidia.com>
Cc: "libc-ports@sourceware.org" <libc-ports@sourceware.org>, 	"joseph@codesourcery.com" <joseph@codesourcery.com>
Content-Type: text/plain; charset=ISO-8859-1
X-SW-Source: 2013-08/txt/msg00015.txt.bz2

Abhishek,

>As I said currently __arch_compare_and_exchange_val_32_acq is defined to __sync_val_compare_and_swap ((mem), (oldval), (newval)), which probably uses two dmb.
>Can't __atomic_compare_exchange_n be used and appropriate memodel be specified for acquire and release variants?
Yes, Looks like that makes sense.
                   thanks, Dinar.