Re: Question about perl while bootstrapping gcc
On 4/17/10, Alan Lehotsky wrote: > Take a look at the at(1) or batch(1) commands if you really want to execute > a command and logout while it's still running. > Or screen(1)
Question on the testsuite.
Hi, 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. Thanks a lot. Vaivaswatha N, Mysore, India
Re: Question on the testsuite.
Vaivaswatha N 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
gcc-4.6-20100417 is now available
Snapshot gcc-4.6-20100417 is now available on ftp://gcc.gnu.org/pub/gcc/snapshots/4.6-20100417/ and on various mirrors, see http://gcc.gnu.org/mirrors.html for details. This snapshot has been generated from the GCC 4.6 SVN branch with the following options: svn://gcc.gnu.org/svn/gcc/trunk revision 158476 You'll find: gcc-4.6-20100417.tar.bz2 Complete GCC (includes all of below) gcc-core-4.6-20100417.tar.bz2 C front end and core compiler gcc-ada-4.6-20100417.tar.bz2 Ada front end and runtime gcc-fortran-4.6-20100417.tar.bz2 Fortran front end and runtime gcc-g++-4.6-20100417.tar.bz2 C++ front end and runtime gcc-java-4.6-20100417.tar.bz2 Java front end and runtime gcc-objc-4.6-20100417.tar.bz2 Objective-C front end and runtime gcc-testsuite-4.6-20100417.tar.bz2The GCC testsuite Diffs from 4.6-20100416 are available in the diffs/ subdirectory. When a particular snapshot is ready for public consumption the LATEST-4.6 link is updated and a message is sent to the gcc list. Please do not use a snapshot before it has been announced that way.
Re: Question on the testsuite.
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 wrote: > From: Ian Lance Taylor > Subject: Re: Question on the testsuite. > To: "Vaivaswatha N" > Cc: gcc@gcc.gnu.org > Date: Saturday, 17 April, 2010, 11:20 PM > Vaivaswatha N > 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 >
