This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: testing consistency
- To: Joe Buck <jbuck at synopsys dot com>
- Subject: Re: testing consistency
- From: Jeffrey A Law <law at hurl dot cygnus dot com>
- Date: Wed, 10 Sep 1997 16:21:01 -0600
- cc: egcs at cygnus dot com (egcs team)
- Reply-To: law at cygnus dot com
In message <199709050148.SAA15882@atrus.synopsys.com>you write:
> I think that I'd like to see a bit more discipline in how we do testing.
> Many of us are doing various tests now, but I do want to make sure that
> we cover the cases that users are likely to use.
I'll second this. It's going to be extremely difficult to get a good
quality release out if everyone isn't bootstrapping and testing in
a similar manner. Bootstrapping with additional flags and testing with
additional flags are useful, but we've got to get the base stuff solid
first.
This is critical to getting a release solidified and out the door.
The first step in this process is to get everyone to bootstrap in the
same manner. Is anyone else using the rough toplevel "bootstrap"
target I posted last week? Comments and improvements are definitely
welcome!
> Ideally, it should be extremely simple to run a "standard test" and
> do a full report of results, and mail it back to a standard address.
> e.g.
>
> ./configure
> make
> make test_and_report
Don't forgot "make install" at the end -- it's been a source of problems
and we need to make sure it works.
Jeff