From owner-sc22wg5@open-std.org Fri Mar 25 20:30:10 2011 Return-Path: X-Original-To: sc22wg5-dom8 Delivered-To: sc22wg5-dom8@www2.open-std.org Received: by www2.open-std.org (Postfix, from userid 521) id 6D9FAC178DC; Fri, 25 Mar 2011 20:30:10 +0100 (CET) X-Original-To: sc22wg5@open-std.org Delivered-To: sc22wg5@open-std.org X-Greylist: delayed 1553 seconds by postgrey-1.18 at www2.open-std.org; Fri, 25 Mar 2011 20:30:09 CET Received: from e2.ny.us.ibm.com (e2.ny.us.ibm.com [32.97.182.142]) by www2.open-std.org (Postfix) with ESMTP id 57331C178DA for ; Fri, 25 Mar 2011 20:30:08 +0100 (CET) Received: from d01dlp02.pok.ibm.com (d01dlp02.pok.ibm.com [9.56.224.85]) by e2.ny.us.ibm.com (8.14.4/8.13.1) with ESMTP id p2PIjRom017707 for ; Fri, 25 Mar 2011 14:45:27 -0400 Received: from d01relay05.pok.ibm.com (d01relay05.pok.ibm.com [9.56.227.237]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id A7D406E8039 for ; Fri, 25 Mar 2011 15:04:13 -0400 (EDT) Received: from d01av05.pok.ibm.com (d01av05.pok.ibm.com [9.56.224.195]) by d01relay05.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p2PJ4DgP229190 for ; Fri, 25 Mar 2011 15:04:13 -0400 Received: from d01av05.pok.ibm.com (loopback [127.0.0.1]) by d01av05.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p2PJ4DLB005471 for ; Fri, 25 Mar 2011 15:04:13 -0400 Received: from d25ml04.torolab.ibm.com (d25ml04.torolab.ibm.com [9.26.6.105]) by d01av05.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id p2PJ4D4f005468; Fri, 25 Mar 2011 15:04:13 -0400 In-Reply-To: <20110303174947.DD0CAC3BA01@www2.open-std.org> References: <20110303174947.DD0CAC3BA01@www2.open-std.org> To: John.Reid@stfc.ac.uk, fortran standards email list for J3 Cc: j3-bounces@j3-fortran.org, WG5 MIME-Version: 1.0 Subject: Re: (j3.2006) (SC22WG5.4408) WG informal ballot X-KeepSent: 4BD65D14:7A5AA065-8525785E:00675F19; type=4; name=$KeepSent X-Mailer: Lotus Notes Release 8.0.1 HF105 April 10, 2008 Message-ID: From: Jim Xia Date: Fri, 25 Mar 2011 15:04:11 -0400 X-MIMETrack: Serialize by Router on D25ML04/25/M/IBM(Release 8.5.1FP4|July 25, 2010) at 03/25/2011 15:04:12, Serialize complete at 03/25/2011 15:04:12 Content-Type: multipart/alternative; boundary="=_alternative 0068BFFD8525785E_=" X-Content-Scanned: Fidelis XPS MAILER Sender: owner-sc22wg5@open-std.org Precedence: bulk This is a multipart message in MIME format. --=_alternative 0068BFFD8525785E_= Content-Type: text/plain; charset="US-ASCII" > > Please answer the following question "Is N1814 ready for forwarding to SC22 > as the PDTR?" in one of these ways. > > 1) Yes. > 2) Yes, but I recommend the following changes. > 3) No, for the following reasons. > 4) Abstain. No, for the following reasons 1.) allow the same C descriptor to be used in CFI_setpointer(). This is a bad idea to begin with, and will cause grief in compiler optimizers. 2.) there are apparent overlapping functionality between CFI_setpointer() and CFI_section(). It's confusing to understand exactly which does what, or when to use which. It's also not clear to me which one will result in zero-based array section or one-based array section. 3.) allow Fortran ALLOCATABLE variables to be allocated on one side (C or Fortran) and then deallocated from the other side. This likely will cause many implementation difficulties. Jim Xia Compiler Testing, X10 & XLF IBM Toronto Lab at 8200 Warden Ave, Markham, On, L6G 1C7 905-413-3444 --=_alternative 0068BFFD8525785E_= Content-Type: text/html; charset="US-ASCII"
>
> Please answer the following question "Is N1814 ready for forwarding to SC22
> as the PDTR?" in one of these ways.
>
> 1) Yes.
> 2) Yes, but I recommend the following changes.
> 3) No, for the following reasons.
> 4) Abstain.


No, for the following reasons

1.) allow the same C descriptor to be used in CFI_setpointer().  This is a bad idea to begin with, and will cause grief in compiler optimizers.
2.) there are apparent overlapping functionality between CFI_setpointer() and CFI_section().  It's confusing to understand exactly which does what, or when to use which.  It's also not clear to me which one will result in zero-based array section or one-based array section.
3.) allow Fortran ALLOCATABLE variables to be allocated on one side (C or Fortran) and then deallocated from the other side.  This likely will cause many implementation difficulties.



Jim Xia

Compiler Testing, X10 & XLF
IBM Toronto Lab at 8200 Warden Ave,
Markham, On, L6G 1C7
905-413-3444

--=_alternative 0068BFFD8525785E_=--