From owner-sc22wg5@open-std.org Thu Jan 29 02:19:07 2009 Return-Path: X-Original-To: sc22wg5-dom7 Delivered-To: sc22wg5-dom7@www2.open-std.org Received: by www2.open-std.org (Postfix, from userid 521) id CB9D4C178D9; Thu, 29 Jan 2009 02:19:07 +0100 (CET) X-Original-To: sc22wg5@open-std.org Delivered-To: sc22wg5@open-std.org Received: from mail.jpl.nasa.gov (sentrion1.jpl.nasa.gov [128.149.139.105]) by www2.open-std.org (Postfix) with ESMTP id B883EC178D6 for ; Thu, 29 Jan 2009 02:19:06 +0100 (CET) Received: from mprox2.jpl.nasa.gov (mprox2.jpl.nasa.gov [137.78.160.141]) by mail.jpl.nasa.gov (Switch-3.3.2mp/Switch-3.3.2mp) with ESMTP id n0T1J2EY007055 for ; Thu, 29 Jan 2009 01:19:03 GMT Received: from [137.79.7.57] (math.jpl.nasa.gov [137.79.7.57]) (authenticated bits=0) by mprox2.jpl.nasa.gov (Switch-3.2.6/Switch-3.2.6) with ESMTP id n0T1J16m012040 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Wed, 28 Jan 2009 17:19:01 -0800 Subject: Re: (j3.2006) (SC22WG5.3930) Two requirements for critical software at JPL From: Van Snyder Reply-To: Van.Snyder@jpl.nasa.gov To: sc22wg5 In-Reply-To: <4980F1A3.5020906@cray.com> References: <20090128214406.86E15C178D6@www2.open-std.org> <4980F1A3.5020906@cray.com> Content-Type: text/plain Organization: Yes Date: Wed, 28 Jan 2009 17:19:00 -0800 Message-Id: <1233191941.15119.1153.camel@math.jpl.nasa.gov> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-8.el5_2.3) Content-Transfer-Encoding: 7bit X-Source-IP: math.jpl.nasa.gov [137.79.7.57] X-Source-Sender: Van.Snyder@jpl.nasa.gov X-AUTH: Authorized Sender: owner-sc22wg5@open-std.org Precedence: bulk On Wed, 2009-01-28 at 16:00 -0800, Bill Long wrote: > I would note that our compiler (as a C program itself) contains an > enormous number of asserts. They help in pinpointing bugs closer to > the point where something went wrong (as opposed to much farther down > the execution sequence when the consequences of the bug manifest as a > fatal error). As such they are useful. We also get complaints that > the compiler is slow. For a compiler that's not horribly serious. > For production Fortran code poor performance is a non-starter. > Different environments and different objectives. At a minimum, if we > wanted asserts in Fortran, there would have to be a simple way to make > them appear to be comments to the compiler. (Basically the old "D" > lines.) Dick's proposal (04-212) suggested something aimed in that direction. Dan's proposals (04-14[234]) had more more concrete features aimed in that direction. -- Van Snyder | What fraction of Americans believe Van.Snyder@jpl.nasa.gov | Wrestling is real and NASA is fake? Any alleged opinions are my own and have not been approved or disapproved by JPL, CalTech, NASA, the President, or anybody else.