From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,48942bcd105c88c6 X-Google-Attributes: gid103376,public From: l117593@cliffy.lfwc.lockheed.com (Cordes MJ) Subject: Re: Computer beats Kasparov Date: 1996/02/26 Message-ID: <4gqufh$m71@cliffy.lfwc.lockheed.com>#1/1 X-Deja-AN: 141126127 references: <4g29e2$ea0$1@mhadg.production.compuserve.com> <4gmbdi$rib@toads.pgh.pa.us> organization: Lockheed Martin Tactical Aircraft Systems newsgroups: comp.lang.ada Date: 1996-02-26T00:00:00+00:00 List-Id: Tore Joergensen (tore@lis.pitt.edu) wrote: : ... If you make machines for : hospitals or air planes, it doesn't sound like a good idea to : say "This code is very fast, and testing seems to indicate that : it does what it is supposed to do". You may say that this is : more or less the same thing that we can say about optimized : code made by a compiler, but at least we can understand the : optimizations and choose to use only optimizations that we are : sure works properly. It is a bit harder if the compiler does : something one place that makes a big difference in the code : another place, just because it seems like a good thing to : do (I can't give you an example, but that is part of the : problem :-). I guess that what I'm saying is: Neural networks : is, or will maybe soon be, good enough to make fast assembly : code from higher level languages, but as long as it isn't : fully understood I doubt that it will be accepted for critical : tasks. ... As long as generated code is identical each time you compile the same code, it doesn't matter if the code generator uses AI. We use an Ada compiler to generate safety critical embedded SW and have seen code generation errors with code generators using common optimization techniques. The bottom line is that we always test the code in order to catch design errors, code errors, and yes, compiler errors. -- --------------------------------------------------------------------- Michael J Cordes Phone: (817) 935-3823 Fax: (817) 935-3800 EMail: CordesMJ@lfwc.lockheed.com ---------------------------------------------------------------------