This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: libio testsuite: timeout compiling tFile.cc
- To: dave at hiauly1 dot hia dot nrc dot ca (John David Anglin)
- Subject: Re: libio testsuite: timeout compiling tFile.cc
- From: "John David Anglin" <dave at hiauly1 dot hia dot nrc dot ca>
- Date: Wed, 30 Aug 2000 19:34:55 -0400 (EDT)
- Cc: gcc-bugs at gcc dot gnu dot org
> The following failure in the libio testsuite occurs occurs on my machine
> (a 735) because of a timeout while compiling tFile.cc:
>
> Running ../../../../libio/testsuite/libio.tests/tFile.exp ...
> Executing on host: /xxx/gnu/gcc-2.96/objdir/gcc/xgcc -B/xxx/gnu/gcc-2.96/objdir/gcc/ ../../../../libio/testsuite/../tests/tFile.cc -O3 -I.. -I../../../../libio/testsuite/.. -nostdinc++ -I/xxx/gnu/gcc-2.96/libstdc++ -I/xxx/gnu/gcc-2.96/libstdc++/stl -L/xxx/gnu/gcc-2.96/objdir/hppa1.1-hp-hpux10.20/threads/libstdc++ -L/xxx/gnu/gcc-2.96/objdir/hppa1.1-hp-hpux10.20/threads/libiberty -L/xxx/gnu/gcc-2.96/objdir/hppa1.1-hp-hpux10.20/threads/libiberty -g -lstdc++ -liberty -lm -threads -o /xxx/gnu/gcc-2.96/objdir/hppa1.1-hp-hpux10.20/libio/testsuite/tFile (timeout = 300)
> WARNING: program timed out.
> compiler exited with status 1
> FAIL: tFile.cc compilation
You might say that running the test at `-O3' is the problem. However,
the time and memory required to compile at `-O2' is essentially identical
the `-O3'. Since this test is not really to test the capability of
the compiler to inline functions, I think the solution is to use the
`-fno-inline' option:
# time /xxx/gnu/gcc-2.96/objdir/gcc/xgcc -B/xxx/gnu/gcc-2.96/objdir/gcc/ -O2 -
g -threads tFile.ii -S
user 9m47.300s
sys 1m1.640s
# time /xxx/gnu/gcc-2.96/objdir/gcc/xgcc -B/xxx/gnu/gcc-2.96/objdir/gcc/ -O3 -
fno-inline -g -threads tFile.ii -S
user 0m18.250s
sys 0m0.430s
Dave
--
J. David Anglin dave.anglin@nrc.ca
National Research Council of Canada (613) 990-0752 (FAX: 952-6605)