public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk>
To: <guerby@acm.org>
Cc: <gcc@gcc.gnu.org>
Subject: Re: ACATS
Date: Thu, 06 Dec 2001 15:00:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.33.0112062239140.21076-100000@kern.srcf.societies.cam.ac.uk> (raw)
In-Reply-To: <200112062222.fB6MMkv02776@ulmo.localdomain>

On Thu, 6 Dec 2001 guerby@acm.org wrote:

> self: I'm no CVS specialist, keeping things in ACATS original form
> will require maintaining piles of dubious scripts at best, I don't
> want to do that myself, I by far prefer the hand crafted approach, and
> have things directly in GCC usable form in CVS.

The point of using the vendor branch is to have *both* the original form
(on the vendor branch) and the GCC version (on the mainline) in CVS - and
when a new version is imported onto the vendor branch, CVS should be able
to help with a lot of the work of merging onto the mainline.  The CVS
experts here can probably provide step-by-step instructions for doing this
and indications of the pitfalls.

> Geoff Keating: You do plan to use dejagnu to run the tests, correct?
> 
> self: My initial tarball will only contain readily compilable sources,
> a list of test main names and attributes as described above,
> documentation on the test to run and omitted, and a minimalistic
> Bourne shell script to run the thing.  From there, I assume DejaGNU
> experts will volunteer or guide volunteers on how to best integrate
> this in the existing Makefile + dg scripts. I must admit I'm not
> really impressed by the existing testing framework, and I believe and
> I can do much better with not that much effort, I'll propose something
> later on, but I don't want this to delay inclusion of ACATS in usable
> form in the GCC project, and I certainly don't want to stop people
> that would volunteer on integrating ACATS and existing DejaGNU.
> People will also have to decide what is officially part of the
> mandatory testing process.

I think DejaGNU must be a requirement for this to be part of the standard
"make check".  As well as providing support for testing cross-compilers in
many different environments, both simulators and target boards, many
people have scripts that use DejaGNU-format .sum files to check for
regressions and analyse results.  For example, that's what the automated
regression checker uses, and it must be desirable for the regression
checker to run these tests.

-- 
Joseph S. Myers
jsm28@cam.ac.uk

  reply	other threads:[~2001-12-06 22:44 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-06 14:32 ACATS guerby
2001-12-06 15:00 ` Joseph S. Myers [this message]
2001-12-06 15:06   ` ACATS Florian Weimer
2001-12-06 15:08 ACATS Richard Kenner
2001-12-06 15:12 ACATS Richard Kenner
2004-04-29 13:12 ACATS John R. Shannon
2004-04-29 13:44 ` ACATS Dave Korn
2004-04-29 13:55   ` ACATS John R. Shannon
2004-04-29 14:10     ` ACATS Dave Korn
2004-04-29 17:11       ` ACATS John R. Shannon
2004-04-29 18:32         ` ACATS Dave Korn
2004-04-29 18:46           ` ACATS John R. Shannon
2004-04-29 19:46 ACATS Richard Kenner
2004-04-29 20:46 ` ACATS John R. Shannon
2004-04-29 20:55 ACATS Richard Kenner
2004-04-29 21:14 ACATS Richard Kenner
2004-04-30  1:48 ` ACATS Zack Weinberg
2004-05-03 20:39   ` ACATS Mark Mitchell

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=Pine.LNX.4.33.0112062239140.21076-100000@kern.srcf.societies.cam.ac.uk \
    --to=jsm28@cam.ac.uk \
    --cc=gcc@gcc.gnu.org \
    --cc=guerby@acm.org \
    /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).