From: Erik Christiansen <erik@dd.nec.com.au>
To: Hans-Peter Nilsson <hp@bitrange.com>
Cc: binutils@sources.redhat.com, "Dmitry K." <dmixm@marine.febras.ru>
Subject: Re: Testsuite for avr-as
Date: Tue, 07 Dec 2004 04:38:00 -0000 [thread overview]
Message-ID: <20041207042355.GC732@dd.nec.com.au> (raw)
In-Reply-To: <Pine.BSF.4.58.0412062000000.65411@dair.pair.com>
On Mon, Dec 06, 2004 at 08:11:45PM -0500, Hans-Peter Nilsson wrote:
> On Tue, 7 Dec 2004, Erik Christiansen wrote:
> > a) Preferred method for generating .d files.
>
> Method? Hah! The output of either objdump or readelf
> redirected, then inspected for sanity and edited to regexpify
> the contents.
Your one sentence is more valuable than the whole DejaGNU manual, at the
moment. Digesting that edifice, in order merely to comprehend the
permissible .d grammar, is a steep climb.
We were wondering how best to handle permissible variability in the
output. You've answered that question too! :-)
> > b) Rather than further develop our existing prototype test engines, what
> > script does binutils use to bang through the .s/.d pairs?
>
> Something tells me you're not aware how the DejaGNU-based
> testsuite (usually) works. Build binutils, then run "make -k
> check" and watch DejaGnu load and execute the various .exp files
> and run whatever is said there, usually using stuff from the
> installed DejaGnu and gas/testsuite/gas/lib. (You can do this
> for AVR if you want; some tests are generic.)
I tried running "make -k check" in my obj-avr/, to see if anything
interesting happened. It was kind enough to create a new site.exp file.
Now I just need to figure out how to connect that to our .s/.d pairs,
rather than hare off after " build_triplet i686-pc-linux-gnu", etc.
(A bit of RTFM should help, in time.)
But for a start, your simplest case may suffice:
[snip]
> Sometimes you want to just check that the assembly listing looks
> about right. See gas/testsuite/gas/mmix/mmix-list.exp.
> Usually the test iterates over ".l" files.
Some quick results, using DejaGnu-compatible .s/.d pairs, would be very
motivating, so I'm even tempted to refresh my TCL acquaintance, and try
just running them through "regexp_diff", once I figure out whether it's
a built-in, or we have to borrow it from one of the scripts.
To bash through a slab of .s/.d pairs for an assembler, which should
give very consistent output, regexp_diff and our 8-line bash script
would do the job, I suspect. Once some more test cases are happening,
the layers of DejaGnu flexibility-providing obfuscation could then be a
second step.
Thanks very much for your help!
Erik
next prev parent reply other threads:[~2004-12-07 4:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-07 0:47 Erik Christiansen
2004-12-07 1:11 ` Hans-Peter Nilsson
2004-12-07 4:38 ` Erik Christiansen [this message]
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=20041207042355.GC732@dd.nec.com.au \
--to=erik@dd.nec.com.au \
--cc=binutils@sources.redhat.com \
--cc=dmixm@marine.febras.ru \
--cc=hp@bitrange.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).