public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Toon Moene <toon@moene.indiv.nluug.nl>
To: Joel Sherrill <joel@OARcorp.com>
Cc: egcs@cygnus.com
Subject: Re: EGCS-970929 and GNAT-3.10p?
Date: Thu, 23 Oct 1997 13:54:00 -0000	[thread overview]
Message-ID: <9710231917.AA22496@moene.indiv.nluug.nl> (raw)
In-Reply-To: <Pine.BSF.3.96.971018104109.13138B-100000@vespucci.advicom.net>

Me:

> [ I did play with the thought to build GNAT in combination with g77  
> before the EGCS project emerged, simply to get a better grip on the  
> regressions g77's backend patches might generate and because people  
> were asking us (fortran@gnu.ai.mit.edu) how to build this
> combination.  I gave up on this once I read that the GNAT test
> suite is proprietary ;-( ]

Joel:

>  A lot of the code used to test an Ada compiler is freely
>  available.  For example, the Ada Compiler Validatation
>  suite is free.  The setup and configuration of it is
>  compiler dependent and that part is proprietary.  There
>  are large bodies of performance suites like PIWG which
>  are freely available.

Took me some time to get to the information I thought I had read -  
DejaNews to the rescue !

Power Search, Old database, search string "ada test suite dewar"  
gives you:

Subject: Re: Towards a free GNU Ada

Note that this kind of regression testing is out of reach
of informal fiddling. For one thing, the great majority of
the code in the critical regression suite is proprietary,
for example it includes large chuncks of the DEC test suite,
as well as a lot of customer code, that the customer has
been willing to entrust to us only on the basis that we will
carefully protect it. It is also the case that the
configuration control that is needed requires very strong
control and management.

Straight from the horse's mouth ...

Of course I needed the regression tests for what I wanted (see above).

HTH,
Toon.

  reply	other threads:[~1997-10-23 13:54 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-10-08 14:14 Greg Galloway
1997-10-08 21:19 ` Jeffrey A Law
1997-10-09  9:26   ` Joel Sherrill
1997-10-09 16:31     ` Jim Wilson
1997-10-15 21:43     ` Jeffrey A Law
1997-10-16  2:35       ` Klaus Kaempf
1997-10-16  8:31         ` Jeffrey A Law
1997-10-16 12:53       ` Jim Wilson
1997-10-16 15:19         ` Jeffrey A Law
1997-10-16 15:19         ` Joel Sherrill
1997-10-16 15:19       ` Joel Sherrill
1997-10-16 15:19         ` Jeffrey A Law
1997-10-16 21:51           ` Richard Henderson
1997-10-16 23:09             ` egcs-971016 Oleg Krivosheev
1997-10-17 14:36               ` egcs-971016 Jeffrey A Law
1997-10-17  5:26             ` EGCS-970929 and GNAT-3.10p? Joel Sherrill
1997-10-17 15:05               ` Toon Moene
1997-10-18  8:45                 ` Joel Sherrill
1997-10-23 13:54                   ` Toon Moene [this message]
1997-10-23 12:49                     ` Joel Sherrill
1997-10-09 16:12   ` Jim Wilson
1997-10-09  9:26 Greg Galloway
1997-10-09 16:12 ` Jim Wilson
1997-10-15 20:16   ` Jeffrey A Law
1997-10-16 12:50     ` Jim Wilson
1997-10-16 12:50 Greg Galloway
1997-10-16 12:53 ` Jeffrey A Law

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9710231917.AA22496@moene.indiv.nluug.nl \
    --to=toon@moene.indiv.nluug.nl \
    --cc=egcs@cygnus.com \
    --cc=joel@OARcorp.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).