public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mike Stump <mikestump@comcast.net>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	Hans Boehm <hans_boehm@hp.com>, Paolo Bonzini <bonzini@gnu.org>,
	Ben Elliston <bje@gnu.org>,
	Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Subject: Re: [testsuite, build] Convert boehm-gc testsuite to DejaGnu (PR boehm-gc/11412)
Date: Fri, 18 Feb 2011 08:34:00 -0000	[thread overview]
Message-ID: <2F36C312-AD33-470E-8169-EFE733661C01@comcast.net> (raw)
In-Reply-To: <ydd62u3p6m7.fsf@manam.CeBiTec.Uni-Bielefeld.DE>

On Jan 5, 2011, at 10:06 AM, Rainer Orth wrote:
>  I see lots of opportunities for code reuse here: most DejaGnu tools in
>  GCC started off as a copy of some other tool with search-and-replace
>  of the tool name and only a few (if any) local changes.  This is a
>  total mess to understand and maintain and I hope to do something about
>  this in the future.

:-)  You now can, though, bear in mind, once you have a delegation neuron, and multiple inheritance neurons (ok, stop laughing at me)...  the design of dejagnu is slightly cleaner than at first blush.

If you've ever seen it wired up to telnet to a terminal server to connect to the serial console on a PC running dos, controled from a real unix machine, to test an entire toolchain (compiler, gdb and so on), you can start to gain some appreciation.  Though, I admit, if you only ever do native testing, the thing is hard to read, convoluted and mysterious.  If someone know of a good programming methodology to allow for the complexity, but hide it for most people, love to have a pointer...  I'd love such a system.

If you ever seen that, and the PC talking to a mips target, and seen it test 5 boards at once, it is sweet.

  parent reply	other threads:[~2011-02-18  8:18 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-05 18:15 Rainer Orth
2011-01-05 20:24 ` Dave Korn
2011-01-05 20:43   ` Joseph S. Myers
2011-01-05 20:58     ` Dave Korn
2011-01-10 10:50       ` Rainer Orth
2011-02-18  8:02   ` Mike Stump
2011-01-05 20:25 ` Dave Korn
2011-01-10 10:55   ` Rainer Orth
2011-01-10 12:02     ` IainS
2011-02-18  8:18   ` Mike Stump
2011-02-22 17:10     ` Rainer Orth
2011-01-06 21:49 ` Ralf Wildenhues
2011-01-10 10:44   ` Rainer Orth
2011-02-18  8:21     ` Mike Stump
2011-01-17 13:31   ` Rainer Orth
2011-01-17 14:04     ` IainS
2011-01-17 14:34       ` Rainer Orth
2011-01-24 15:05       ` Rainer Orth
2011-01-24 16:31         ` IainS
2011-01-24 16:43           ` Rainer Orth
2011-02-18  9:50         ` Mike Stump
2011-02-22 17:40           ` Rainer Orth
2011-03-21 13:00           ` Rainer Orth
2011-03-21 18:28             ` Mike Stump
2011-03-21 18:33               ` Paolo Bonzini
2011-03-21 18:54                 ` Mike Stump
2011-03-23  9:01                 ` Rainer Orth
2011-03-21 18:33               ` Rainer Orth
2011-03-25 10:39             ` Paolo Bonzini
2011-03-25 10:59               ` Paolo Bonzini
2011-03-25 17:10               ` Rainer Orth
2011-03-25 17:17                 ` Rainer Orth
2011-03-27 16:35                   ` H.J. Lu
2011-01-18 20:51     ` Ralf Wildenhues
2011-01-20 18:03       ` Rainer Orth
2011-02-18  8:34 ` Mike Stump [this message]
2011-02-22 17:37   ` Rainer Orth
2011-02-22 22:07     ` Mike Stump

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=2F36C312-AD33-470E-8169-EFE733661C01@comcast.net \
    --to=mikestump@comcast.net \
    --cc=Ralf.Wildenhues@gmx.de \
    --cc=bje@gnu.org \
    --cc=bonzini@gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hans_boehm@hp.com \
    --cc=ro@CeBiTec.Uni-Bielefeld.DE \
    /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).