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, an
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
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 (
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 cou
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)