From owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org Thu Mar 15 19:51:17 2012 Return-Path: X-Original-To: sc22wg5-dom8 Delivered-To: sc22wg5-dom8@www.open-std.org Received: by www.open-std.org (Postfix, from userid 521) id 1144B356973; Thu, 15 Mar 2012 19:51:16 +0100 (CET) Delivered-To: sc22wg5@open-std.org X-Greylist: delayed 2380 seconds by postgrey-1.34 at www5.open-std.org; Thu, 15 Mar 2012 19:51:16 CET Received: from proofpoint5.lanl.gov (proofpoint5.lanl.gov [204.121.3.53]) by www.open-std.org (Postfix) with ESMTP id 52ABD35696A for ; Thu, 15 Mar 2012 19:51:15 +0100 (CET) Received: from mailrelay1.lanl.gov (mailrelay1.lanl.gov [128.165.4.101]) by proofpoint5.lanl.gov (8.14.4/8.14.4) with ESMTP id q2FIBMPY019011; Thu, 15 Mar 2012 12:11:22 -0600 Received: from cic-mail.lanl.gov (cic-mail.lanl.gov [128.165.4.115]) by mailrelay1.lanl.gov (Postfix) with ESMTP id 82D45E107D6; Thu, 15 Mar 2012 12:11:16 -0600 (MDT) Received: from localhost (localhost.localdomain [127.0.0.1]) by cic-mail.lanl.gov (Postfix) with ESMTP id 7F7CE3160096; Thu, 15 Mar 2012 12:11:16 -0600 (MDT) X-NIE-2-Virus-Scanner: amavisd-new at cic-mail.lanl.gov Received: from kirkegaard.lanl.gov (kirkegaard.lanl.gov [128.165.148.117]) by cic-mail.lanl.gov (Postfix) with ESMTP id 6215E316008B; Thu, 15 Mar 2012 12:11:16 -0600 (MDT) Subject: Re: (j3.2006) (SC22WG5.4652) AW: Vote on N1904 Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Craig Rasmussn In-Reply-To: <20120315132645.357C59DB112@www.open-std.org> Date: Thu, 15 Mar 2012 12:11:16 -0600 Cc: Reinhold Bader , "Rolf Rabenseifner (rabenseifner@hlrs.de)" , WG5 , Jeff Squyres Content-Transfer-Encoding: quoted-printable Message-Id: References: <20120312152923.857DB9DB112@www.open-std.org> <20120314164259.A5DD4356A46@www.open-std.org> <20120314215009.D830F9DB112@www.open-std.org> <20120315132645.357C59DB112@www.open-std.org> To: fortran standards email list for J3 X-Mailer: Apple Mail (2.1084) X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.6.7498,1.0.260,0.0.0000 definitions=2012-03-15_04:2012-03-15,2012-03-14,1970-01-01 signatures=0 Sender: owner-sc22wg5@open-std.org Precedence: bulk The intent (surely, no pun intended) for MPI-3 receive buffers was to = stay away from requirement that "the dummy argument becomes undefined on = invocation of the procedure." Thus all of the MPI-3 TYPE(*) dummy = arguments are either INTENT(IN) or no intent is specified. Would appreciate advice if anyone believes that this was the wrong = decision. -craig On Mar 15, 2012, at 7:26 AM, Reinhold Bader wrote: > I managed to check the latest draft of the new Fortran MPI-3 interface = today - > receive buffers are not specified with any INTENT. >=20 > INTENT(OUT) is specified for some other arguments in MPI-3 calls, like = MPI > request handles or the error argument, but all these cases do not use > TYPE(*). >=20 > Regards > Reinhold >=20 > Am 14.03.2012 22:49, schrieb Bader, Reinhold: >> [...] >>> Note that the proposals to simply forbid INTENT(OUT) together with >>> assumed-type exclude reasonable uses of INTENT(OUT) (e.g. for MPI >>> receive buffers), but some constraint along those lines seems the = best >>> solution. >>=20 >> The MPI-3 draft for the new Fortran bindings contains some remarks >> concerning INTENT(OUT) for receive buffers which - if I remember >> correctly - can be interpreted along the following lines >>=20 >> * don't take the Fortran semantics of the MPI spec too seriously as = an implementor - >> you're allowed to specify INTENT(INOUT) here [and would be = required to >> if you use TYPE(*) and the above restriction is implemented in the = TS] >> * programmer, please don't rely on other things than the buffer = elements >> written by your send NOT becoming undefined >>=20 >> Rolf may be able to shed more light on this, so am putting him on CC = here. >> In any case, it is not the purpose of MPI-3 to enable communication = of >> data of types described below, so while I'm not convinced that = loosening >> of the planned INTENT(OUT) prohibition is necessary, the below would >> certainly not impact MPI-3. >>=20 >>> The following is badly worded and may not be enough, but is >>> put forward as a possibility: >>> "If the actual argument corresponding to an assumed-type dummy = argument >>> is of a type with default-initialized components, or of a type that = has >>> has components that have the ALLOCATABLE or POINTER attributes, or = are >>> of types with default-initialized components, the assumed-type = entity >>> shall not have the INTENT(OUT) attribute." >>>=20 >> Regards >> Reinhold >=20 >=20 > --=20 > Dr. Reinhold Bader >=20 > Leibniz Supercomputing Centre (http://www.lrz.de) / HPC Support > Tel. +49 89 35831 8825 - Fax +49 89 35831 8625 >=20 > _______________________________________________ > J3 mailing list > J3@j3-fortran.org > http://j3-fortran.org/mailman/listinfo/j3