libio testsuite: timeout compiling tFile.cc

[Jeffrey A Law]

  In message <200008302238.SAA25954@hiauly1.hia.nrc.ca>you write:
  > 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/ob
  > jdir/gcc/ ../../../../libio/testsuite/../tests/tFile.cc  -O3 -I.. -I../../.
  > ./../libio/testsuite/..  -nostdinc++ -I/xxx/gnu/gcc-2.96/libstdc++ -I/xxx/g
  > nu/gcc-2.96/libstdc++/stl -L/xxx/gnu/gcc-2.96/objdir/hppa1.1-hp-hpux10.20/t
  > hreads/libstdc++ -L/xxx/gnu/gcc-2.96/objdir/hppa1.1-hp-hpux10.20/threads/li
  > biberty  -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 
  > 
  > I ran the compilation manually and it does complete successfully.  However,
  > the resources needed to compile tFile are now quite large and can cause
  > vm thrashing on older machines with limited memory.  The user and sys times
  > for the compilation with 2.96 were:
  > 
  > user    9m41.150s
  > sys     0m57.850s
  > 
  > The virtual memory required by cc1plus was approximately 65MB at its peak.
  > 
  > In any case, I think the timeout values need to be increased for the
  > three tFile.cc compilations in tFile.exp unless the performance of cc1plus
  > can be improved.
I'd rather see us do the work to improve the compile times.

You might be able to move this process along by trying to identify the hot
spots so that we can fix them.  

jeff