This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: ACATS & GCC testsuite
- From: Zack Weinberg <zack at codesourcery dot com>
- To: Laurent Guerby <guerby at acm dot org>
- Cc: Richard Kenner <kenner at vlsi1 dot ultra dot nyu dot edu>, "gcc at gcc dot gnu dot org" <gcc at gcc dot gnu dot org>
- Date: Wed, 02 Apr 2003 12:45:04 -0800
- Subject: Re: ACATS & GCC testsuite
- References: <10303281144.AA28312@vlsi1.ultra.nyu.edu><1048852101.10770.117.camel@localhost.localdomain>
Laurent Guerby <guerby at acm dot org> writes:
>> That's why I by far prefer to have the testing being done after
>> install, and not in build like it is done for GCC via DejaGNU now.
>>
>> No, builds seem right. I don't want to have to install a compiler in
>> order to test it.
>
> That's a developper argument, and it's not that strong:
> testing C takes 43 minutes, Ada 44 minutes, and install is 1 minute
> and less than 70 MB (that two years of daily builds
> on a 40GB el cheapo disk, easy to spot regression then :).
When developing a patch I frequently sit in a cycle like this:
<edit edit edit>
$ make cc1
$ make check-gcc RUNTESTFLAGS="only/the/subset/I/care/about.exp"
FAIL: ...
<repeat>
I would not mind much if final acceptance testing for patches was done
on an installed tree, but I'll be unhappy if you break the above.
zw