[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Interpreting gcc-3.3 "make check" results

From: Dan Kegel
Subject: Re: Interpreting gcc-3.3 "make check" results
Date: Thu, 12 Jun 2003 10:07:12 -0700
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030529

Doug Evans wrote:
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


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.

Thanks, I'd seen that syntax and the just-one-expfile argument
to runtest, but I was always fuzzy about whether you had to
specify a path.  I guess that's one more nugget for the
"how to test gcc with dejagnu" tutorial I'm writing.
- Dan

Dan Kegel

reply via email to

[Prev in Thread] Current Thread [Next in Thread]