This is the mail archive of the
cgen@sources.redhat.com
mailing list for the CGEN project.
Re: gas-test target
- To: Ben Elliston <bje at cygnus dot com>
- Subject: Re: gas-test target
- From: Dave Brolley <brolley at redhat dot com>
- Date: Wed, 01 Nov 2000 11:25:09 -0500
- CC: Doug Evans <dje at transmeta dot com>, cgen development <cgen at sources dot redhat dot com>
- Organization: Red Hat Canada, Inc
- References: <Pine.LNX.4.30.0011011844430.16854-100000@moshpit.cygnus.com>
Ben Elliston wrote:
>
> Hi Dave,
>
> > I wanted to first inspect the result, then run it by hand.
> > I'd mull this over for awhile before checking it in.
>
> At the very least we need to be able to run it after hand tweaking it.
> This is the way I add scenarios to the test, since tweaking both the
> allinsn.s and allinsn.d files (especially the second) can be a major
> hassle. So all I ask is that we end up with a separate target to run
> it without regenerating it.
>
> I agree; it would be very convenient to be able to do this quickly.
> Do you think a `gas-dump' target in the cgen Makefile would suffice?
>
> Ben
How about gas-create-test and gas-gen-test? gas-dump doesn't seem
to convey the right meaning for me.
I thought about this a little more and it seems to me that the
generated script should be part of the source tree and checked
into the repository, since the best way to update the testsuite
is to edit it and run it again. Currently, I keep a copy of the
script stashed away in case I need to update the testsuite.
What does everyone think?
Dave