comp.lang.ada
 help / color / mirror / Atom feed
From: l117593@cliffy.lfwc.lockheed.com (Cordes MJ)
Subject: Re: Elaboration order
Date: 1996/03/21
Date: 1996-03-21T00:00:00+00:00	[thread overview]
Message-ID: <4isl6j$pll@cliffy.lfwc.lockheed.com> (raw)
In-Reply-To: dewar.827293943@schonberg

Robert Dewar (dewar@cs.nyu.edu) wrote:
: Mike says

: "As an aside to the RM discussion of this thread, how do I know
: that Ada compiler X will generate the correct (as defined in
: the RM) elaboration order?

: I know that ACVC tests do not guarantee correct code generation.
: Is the ACVC suite more complete when it comes to elaboration? Is
: there a standard benchmark used by compiler vendors? Or, for safety
: critical functions, should I verify this for every application
: build?"

: Of course the ACVC suite does not guarantee that a compiler gets the
: order of elaboration correct in every case. Your question seems to
: imply that you expected the ACVC suite to guarantee correct code
: generatoin and that the reason that it does not is that it is not
: complete. This is a serious misconception. No test suite can ever
: guarantee that a compiler has no errors -- indeed, except for very
: trivial programs, no set of tests ever guarantees accuracy.


You are reading things into the question which were not there. I was simply 
asking if it was generally held that elaboration order algorithms are
safer or better tested than code generation algorithms.

: For safety critical applications, you cannot trust ANY aspect of a compiler
: or any other tool that you use, and you need to carefully verify EVERYTHING
: about your program -- at least, put it this way, if you write the code for
: a plane that I will fly on, I will expect this!

Not exactly - industry cannot afford to verify *all* aspects of a program.
Risks are identified and analyzed and base on the analysis, something may
be done (e.g., redundancy, backup systems, additional testing). This is
true for all systems which go on a plane - not just SW.

A good software specific example is branch level testing vs path testing.
We do not perform full path testing of our applications because it (path
testing) is not cost effective. We perform other cost effective testing
on the application to reduce any and all risks to reasonable levels.

: Are there ACVC tests to test order of elaboration? Sure!
: Do they help ensure that compilers are correct in this respect? Sure!
: Do they guarantee that compilers are correct in this respect? NO!

THANKS!
--
---------------------------------------------------------------------
Michael J Cordes
Phone: (817) 935-3823
Fax:   (817) 935-3800
EMail: CordesMJ@lfwc.lockheed.com
---------------------------------------------------------------------




  reply	other threads:[~1996-03-21  0:00 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <314701A1.469D@lfwc.lockheed.com>
1996-03-15  0:00 ` Elaboration order Robert I. Eachus
1996-03-15  0:00   ` Robert Dewar
     [not found] ` <1996Mar14.021345.9856@enterprise.rdd.lmsc.lockheed.com>
     [not found]   ` <314829CD.4FA9@lfwc.lockheed.com>
1996-03-15  0:00     ` Tucker Taft
1996-03-15  0:00       ` Ken Garlington
1996-03-16  0:00     ` Joe Wierzbowski
1996-03-26  0:00       ` AdaWorks
1996-03-26  0:00         ` Robert A Duff
1996-03-26  0:00         ` Robert Dewar
1996-03-26  0:00           ` Robert A Duff
1996-03-26  0:00             ` Robert Dewar
1996-03-26  0:00           ` IO in Pure packages, debugging Laurent Guerby
1996-03-16  0:00     ` Elaboration order Ted Dennison
1996-03-26  0:00     ` Laurent Guerby
1996-03-26  0:00       ` Robert A Duff
1996-03-18  0:00 ` Ted Dennison
1996-03-18  0:00 ` Ken Garlington
1996-03-19  0:00 ` Michel Gauthier
1996-03-20  0:00 ` DenReimer
1996-03-20  0:00   ` Robert A Duff
1996-03-20  0:00     ` Norman H. Cohen
1996-03-20  0:00       ` Robert Dewar
1996-03-20  0:00   ` Norman H. Cohen
1996-03-20  0:00   ` Tucker Taft
     [not found] ` <Do8JDv.A2v@world.std.com>
     [not found]   ` <31494143.3825@lfwc.lockheed.com>
1996-03-15  0:00     ` Mark A Biggar
1996-03-18  0:00       ` Ken Garlington
1996-03-19  0:00         ` Norman H. Cohen
1996-03-20  0:00           ` Cordes MJ
1996-03-19  0:00             ` Robert Dewar
1996-03-21  0:00               ` Cordes MJ [this message]
1996-03-21  0:00               ` Ken Garlington
1996-03-20  0:00             ` Robert A Duff
1996-03-20  0:00               ` Cordes MJ
1996-03-20  0:00                 ` Robert A Duff
1996-03-22  0:00                   ` Cordes MJ
1996-03-20  0:00                 ` Robert Dewar
1996-03-21  0:00                   ` Ken Garlington
1996-03-23  0:00                 ` JP Thornley
1996-03-25  0:00                   ` Robert Dewar
1996-03-26  0:00                 ` JP Thornley
1996-03-19  0:00         ` Chris McKnight
1996-03-21  0:00           ` Ken Garlington
1996-03-15  0:00     ` Robert A Duff
1996-03-18  0:00       ` Norman H. Cohen
     [not found]       ` <EACHUS.96Mar18143219@spectre.mitre.org>
1996-03-18  0:00         ` Robert Dewar
1996-03-19  0:00           ` Ted Dennison
1996-03-18  0:00         ` Robert Dewar
1996-03-20  0:00         ` David Emery
1996-03-20  0:00   ` Robert I. Eachus
1996-03-22  0:00   ` Robert I. Eachus
1996-03-22  0:00   ` Robert I. Eachus
1999-11-15  0:00 Elaboration Order Wolf-Dieter Heker
1999-11-15  0:00 ` Robert Dewar
1999-11-16  0:00   ` Wolf-Dieter Heker
1999-11-16  0:00     ` David C. Hoos, Sr.
1999-11-16  0:00     ` Robert Dewar
1999-11-20  0:00       ` Simon Wright
1999-11-22  0:00         ` Robert Dewar
1999-11-23  0:00           ` Mats Weber
1999-11-16  0:00     ` Robert Dewar
1999-11-15  0:00 ` Jean-Pierre Rosen
1999-11-15  0:00   ` Robert Dewar
1999-11-16  0:00     ` Jean-Pierre Rosen
1999-11-20  0:00       ` Simon Wright
  -- strict thread matches above, loose matches on Subject: below --
1996-03-18  0:00 Elaboration order Jean-Pierre Rosen
1996-03-21  0:00 ` Ken Garlington
     [not found] <DoDMLL.1F9@world.std.com>
1996-03-18  0:00 ` Chris McKnight
replies disabled

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox