From owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org Fri Feb 20 17:54:54 2015 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 D71B7358556; Fri, 20 Feb 2015 17:54:54 +0100 (CET) Delivered-To: sc22wg5@open-std.org Received: from esa2.cray.iphmx.com (esa2.cray.iphmx.com [68.232.143.164]) by www.open-std.org (Postfix) with ESMTP id 41A59357222 for ; Fri, 20 Feb 2015 17:54:53 +0100 (CET) X-IronPort-AV: E=Sophos;i="5.09,615,1418083200"; d="scan'208";a="466158" Received: from cray-smtp-2.cray.com (HELO CFWEX01.americas.cray.com) ([136.162.34.11]) by esa2.cray.iphmx.com with ESMTP/TLS/AES128-SHA; 20 Feb 2015 16:54:52 +0000 Received: from CFWEX02.americas.cray.com (172.30.74.25) by CFWEX01.americas.cray.com (172.30.88.25) with Microsoft SMTP Server (TLS) id 14.3.224.2; Fri, 20 Feb 2015 10:54:46 -0600 Received: from CFWEX01.americas.cray.com ([169.254.1.190]) by cfwex02.americas.cray.com ([169.254.2.121]) with mapi id 14.03.0224.002; Fri, 20 Feb 2015 10:54:45 -0600 From: Bill Long To: fortran standards email list for J3 CC: John Reid , WG5 Subject: Re: (j3.2006) (SC22WG5.5449) [ukfortran] Response to TS ballot Thread-Topic: (j3.2006) (SC22WG5.5449) [ukfortran] Response to TS ballot Thread-Index: AQHQTQIb9n3FlKvi8Uy8bienmqlhv5z6Jm0A Date: Fri, 20 Feb 2015 16:54:45 +0000 Message-ID: <5119DAB4-11DD-413B-8735-04C8646CBD4D@cray.com> References: <20150219231019.EF7E83570D2@www.open-std.org> <20150220114055.4BF3C358556@www.open-std.org> In-Reply-To: <20150220114055.4BF3C358556@www.open-std.org> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [192.168.233.140] Content-Type: text/plain; charset="Windows-1252" Content-ID: <2943193B40D87140A8E415C072B18E60@cray.com> Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Sender: owner-sc22wg5@open-std.org Precedence: bulk On Feb 20, 2015, at 5:40 AM, N.M. Maclaren wrote: > On Feb 19 2015, John Reid wrote: >>> Nick Maclaren wrote >> No, for the reasons given in N2038, N2013 and other votes. I need to >> reiterate that neither response in N2039 even addresses my comments. I >> believe that incorporating the TS into the main standard will cause >> serious harm to Fortran, because the (semantic) difficulties cannot be >> resolved (let alone specified unambiguously) in the time available. >> Indeed, it is not clear even that they ARE soluble, because this TS is >> specifying a feature that is beyond the state of the art, and has been >> for half a century. I would be prepared to change my vote to abstain if >> the decision to incorporate it were reversed. >>=20 >> Response >> It is our belief that agreeing to delay to a later revision of the >> Fortran standard would lead to several "no" votes. Failure to >> standardize a resilience capability before compilers implement F2015 >> would lead to vendors implementing incompatible schemes, hurting the >> goal of code portability. >=20 > Whether or not the second statement is true, and it is extremely > unclear whether it is, it is not a response to my objections. I am > asserting that the task is infeasible, for the reasons I gave. >=20 There are differing opinions on whether =93the task is infeasible=94. I t= end to weight higher the opinions of the guys who will end up writing the c= ompiler and runtime code.=20 Cheers, Bill >=20 > Regards, > Nick Maclaren. >=20 > _______________________________________________ > J3 mailing list > J3@mailman.j3-fortran.org > http://mailman.j3-fortran.org/mailman/listinfo/j3 Bill Long = longb@cray.com Fortran Technical Suport & voice: 651-60= 5-9024 Bioinformatics Software Development fax: 651-605-9142 Cray Inc./ Cray Plaza, Suite 210/ 380 Jackson St./ St. Paul, MN 55101