Re: Interpreting gcc-3.3 "make check" results

[Doug Evans <dje at transmeta dot com>]

Dan Kegel writes:
 > > Unfortunately, I don't have any magic recipe for dealing with test
 > > failures.  It seems that you just need to look at them one at a time and
 > > figure out what went wrong, and then decide what to do about it.
 > 
 > Yup.  And see what others have done about 'em.

One useful thing in the gcc testsuite is the ability to run make check
for one particular test.
Usually what I do is run make check, let it finish, and then rename
testsuite/gcc.log so it doesn't get clobbered when I run make check again.

Then go through the tests one by one.
After patching gcc (assuming it's a gcc bug) I can test the patch
for the particular testcase I'm interested in with

make check RUNTESTFLAGS=foo.exp=bar.c

e.g.

make check RUNTESTFLAGS=compile.exp=20010605-1.c

And if you wanted a few -v's:

make check RUNTESTFLAGS='compile.exp=20010605-1.c -v -v'

Sorry about the foo=bar=baz syntax, but I kinda like it.

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com