From owner-sc22wg5@open-std.org  Thu Apr 22 21:09:25 2010
Return-Path: <owner-sc22wg5@open-std.org>
X-Original-To: sc22wg5-dom8
Delivered-To: sc22wg5-dom8@www2.open-std.org
Received: by www2.open-std.org (Postfix, from userid 521)
	id 2B0C6C178E1; Thu, 22 Apr 2010 21:09:25 +0200 (CET DST)
X-Original-To: sc22wg5@open-std.org
Delivered-To: sc22wg5@open-std.org
Received: from mail2.cray.com (mail2.cray.com [136.162.64.100])
	by www2.open-std.org (Postfix) with ESMTP id C9578C178DA
	for <sc22wg5@open-std.org>; Thu, 22 Apr 2010 21:09:18 +0200 (CET DST)
Received: from sealmr01.us.cray.com (sealmr01.us.cray.com [172.28.74.60])
	by mail2.cray.com (8.13.6/8.13.3/gw-5323) with ESMTP id o3MJ9FDk007617
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL);
	Thu, 22 Apr 2010 12:09:15 -0700 (PDT)
Received: from cfexcas01.americas.cray.com (cfexcas01.americas.cray.com [172.30.74.222])
	by sealmr01.us.cray.com (8.14.3/8.14.3/eadURLLastChangedRevision: 5204) with ESMTP id o3MJ9EXe008966;
	Thu, 22 Apr 2010 12:09:14 -0700
Received: from fortran.us.cray.com (172.31.19.200) by
 cfexcas01.americas.cray.com (172.30.74.226) with Microsoft SMTP Server (TLS)
 id 8.1.393.1; Thu, 22 Apr 2010 14:09:14 -0500
Message-ID: <4BD09ED9.6040105@cray.com>
Date: Thu, 22 Apr 2010 14:09:13 -0500
From: Bill Long <longb@cray.com>
Reply-To: <longb@cray.com>
Organization: Cray Inc.
User-Agent: Thunderbird 2.0.0.24 (Macintosh/20100228)
MIME-Version: 1.0
To: fortran standards email list for J3 <j3@j3-fortran.org>
Cc: WG5 <sc22wg5@open-std.org>
Subject: Re: (j3.2006) (SC22WG5.4259)  [ukfortran]  Question on locks
References: <20100421204947.D8CC7C178DA@www2.open-std.org>	<20100421221958.90A94C4E9FA@www2.open-std.org>	<20100422073128.25D2DC178D9@www2.open-std.org> <20100422155329.47692C178D9@www2.open-std.org>
In-Reply-To: <20100422155329.47692C178D9@www2.open-std.org>
Content-Type: text/plain; charset="ISO-8859-1"; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-sc22wg5@open-std.org
Precedence: bulk



Aleksandar Donev wrote:
  So you can simply forget about sync memory, as if it did not
> exist in the standard at all, *unless* you want to go beyond the built-
> in mechanisms.
> 

Or if you are a vendor who needs to include the SYNC MEMORY code in the 
other mechanisms to get the semantics right.

Cheers,
Bill

-- 
Bill Long                                           longb@cray.com
Fortran Technical Support    &                 voice: 651-605-9024
Bioinformatics Software Development            fax:   651-605-9142
Cray Inc./Cray Plaza, Suite 210/380 Jackson St./St. Paul, MN 55101


