Hi, Thanks a lot. Actually, I used to give the same options when I tried manually, but still I didn't get any errors.
Looking at the log made me realise that the testsuite considers anything that is printed to stdout as an error. I used to print a few diagnostic messages for my convenience, and I think the testsuite saw that as an error. Anyway, I commented out the messages and now things seem to be fine. Thanks a lot again. :) Vaivaswatha N, Mysore, India --- On Sat, 17/4/10, Ian Lance Taylor <i...@google.com> wrote: > From: Ian Lance Taylor <i...@google.com> > Subject: Re: Question on the testsuite. > To: "Vaivaswatha N" <vaivaswa...@yahoo.co.in> > Cc: gcc@gcc.gnu.org > Date: Saturday, 17 April, 2010, 11:20 PM > Vaivaswatha N <vaivaswa...@yahoo.co.in> > writes: > > > I was experimenting with some code (tree-ssa-sccvn.c > to be precise), and while doing so, when I ran the > testsuite, I got an error with a file (namely, > "20030125-1.c" in "gcc.c-torture/compile/"). > > > > My problem is, when I copy this file aside and try to > compile it (using the same build of course), I do not get > any error. How is it that the test fails only when run > through the testsuite? I'm kind of lost here as I need to > debug this file and see where it fails. > > Look at gcc/testsuite/gcc/gcc.log to see precisely how the > file is > being compiled by the testsuite when it fails. Search > for the name of > the test, and note that each test is compiled several > different times > with different options. Presumably the testsuite is > failing when > using some combination of options which you are not using. > > Ian >
