public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Erik Christiansen <erik@dd.nec.com.au>
To: binutils@sources.redhat.com
Cc: "Dmitry K." <dmixm@marine.febras.ru>
Subject: Testsuite for avr-as
Date: Tue, 07 Dec 2004 00:47:00 -0000	[thread overview]
Message-ID: <20041207003334.GB732@dd.nec.com.au> (raw)

G'day,

Unlike other gas implementations, avr-as lacks a formal testsuite. Over
on the avr-gcc list, a couple of us are seeking to rectify that. Rather
than go too far with "home-brew" test schemes, we're trying to scrabble
up the binutils testsuite learning curve.

A bit of poking around in the binutils source distribution shows .s and
.d files. Is there some doco that we can read, to discover:

a) Preferred method for generating .d files.
b) Rather than further develop our existing prototype test engines, what
   script does binutils use to bang through the .s/.d pairs?

Oh, a horrible thought: If this is to find its way into the distribution
one day, then there's likely to be some requirements we should know about.

Erik

             reply	other threads:[~2004-12-07  0:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-07  0:47 Erik Christiansen [this message]
2004-12-07  1:11 ` Hans-Peter Nilsson
2004-12-07  4:38   ` Erik Christiansen
2004-12-07 13:06     ` Hans-Peter Nilsson
2004-12-07 13:12       ` Hans-Peter Nilsson
2004-12-08  1:11       ` Erik Christiansen
2004-12-09  6:35       ` Erik Christiansen
2004-12-09 11:20         ` Hans-Peter Nilsson
2004-12-09 11:30           ` Hans-Peter Nilsson
2004-12-10  6:49           ` Erik Christiansen
2004-12-10 12:15             ` Hans-Peter Nilsson
2005-01-20  5:55               ` Erik Christiansen
2005-01-20 12:59                 ` Hans-Peter Nilsson
2005-01-21  8:17                   ` Erik Christiansen

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=20041207003334.GB732@dd.nec.com.au \
    --to=erik@dd.nec.com.au \
    --cc=binutils@sources.redhat.com \
    --cc=dmixm@marine.febras.ru \
    /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).