From: mrs@wrs.com (Mike Stump)
To: carlo@runaway.xs4all.nl, egcs@cygnus.com
Cc: law@cygnus.com
Subject: Re: egcs testsuite & dejagnu : A special case?
Date: Mon, 29 Jun 1998 22:34:00 -0000 [thread overview]
Message-ID: <199806292300.QAA14961@kankakee.wrs.com> (raw)
> From: Carlo Wood <carlo@runaway.xs4all.nl>
> Date: Thu, 25 Jun 1998 17:27:34 +0200 (CEST)
> I investigated this new problem and found that it basically is the
> result of the fact that dejagnu is written to test other packages,
> other packages that need a compiler to be compiled, but that
> definitely are not the compiler itself.
Could you rephrase this?
If you meant to say that dejagnu is not written to test the compiler
itself, then I wonder why you say that, as it was.
> The problem, when needing the package itself to compile the package
> (testsuite executables), has not been addressed in dejagnu.
Could you rephrase this?
If you meant to say that dejagnu doesn't address the problem of
testing executables in egcs that are built with the compiler in egcs,
then I wonder why you say that, as it was.
> My feeling is that this is not really a problem of dejagnu: We can't
> expect them
That them is us. dejagnu exists to test the compiler. That is why it
was written, and that is it's main purpose in life.
> to hardcode support for all the compiler cases into dejagnu,
We all agree here. Cleanliness says that we should use generic
interfaces with as little built in knowledge of the compiler specifics
as we can. dejagnu however is not exactly a model of cleanliness.
> I am more then willing to write the small changes for egcs to make
> it work smoothly, but I'd like to hear a "go" from you before I do
> :). These patches will be logical, but only if you accept the idea
> that testing a package that is a compiler is a special case.
If your changes make it work more often and don't introduce bugs, then
I'd support them. The problem is the later one. If you massively
rearchitect dejagnu and unless you test in many different ways on many
different targets, or are really good, there will be bugs. What is
painful, is if you break testing that does work today. This is why, I
think when it comes to dejagnu, I don't like to see a whole lot of
code motion in it, just a little bit every now and then to fix
specific problems in specific ways.
next reply other threads:[~1998-06-29 22:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-06-29 22:34 Mike Stump [this message]
1998-06-30 15:15 ` Craig Burley
1998-06-30 14:46 ` Jeffrey A Law
[not found] <199807031310.PAA24690@jolan.ppro>
1998-07-03 15:29 ` Craig Burley
-- strict thread matches above, loose matches on Subject: below --
1998-07-01 0:54 Mike Stump
1998-07-01 7:26 ` Craig Burley
1998-07-01 20:20 ` Jeffrey A Law
1998-07-02 11:02 ` Carlo Wood
1998-07-03 0:12 ` Craig Burley
1998-07-03 0:50 ` Carlo Wood
1998-07-03 8:38 ` Craig Burley
1998-07-03 9:35 ` Carlo Wood
1998-06-25 18:53 Carlo Wood
1998-06-26 2:49 ` Manfred Hollstein
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=199806292300.QAA14961@kankakee.wrs.com \
--to=mrs@wrs.com \
--cc=carlo@runaway.xs4all.nl \
--cc=egcs@cygnus.com \
--cc=law@cygnus.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).