regression-checker: Add in new passes during regression.

[Hans-Peter Nilsson <hp at bitrange dot com>]

I copied the regression-checking parts to my own regression
tester and discovered that during a regress-N state, new passes
are not added, so regressions in new tests would then not be
discovered.  I think it's confusing to not see new regressions
during a state of regression, so how about this?
Not tested at all, except that "cat - file" works and that I use
the corresponding change myself and nothing's broke yet.

Index: btest-gcc.sh
===================================================================
RCS file: /cvs/gcc/gcc/contrib/regression/btest-gcc.sh,v
retrieving revision 1.2
diff -p -c -r1.2 btest-gcc.sh
*** btest-gcc.sh	2002/03/09 19:41:11	1.2
--- btest-gcc.sh	2002/03/11 11:09:31
*************** for LOG in $TESTLOGS ; do
*** 156,161 ****
--- 156,170 ----
    L=`basename $LOG`
    awk '/^FAIL: / { print "'$L'",$2; }' $LOG || exit 1
  done | sort | uniq > $FAILED || exit 1
+
+ # Add in new passes since the last run.
+ for LOG in $TESTLOGS ; do
+   L=`basename $LOG`
+   awk '/^PASS: / { print "'$L'",$2; }' $LOG || exit 1
+ done | cat - ${PASSES} | sort | uniq | comm -23 - $FAILED > ${PASSES}~ || exit 1
+ [ -s ${PASSES}~ ] || exit 1
+ mv ${PASSES}~ ${PASSES} || exit 1
+
  comm -12 $FAILED $PASSES >> $REGRESS || exit 1
  NUMREGRESS=`wc -l < $REGRESS | tr -d ' '`
  if [ $NUMREGRESS -ne 0 ] ; then
*************** if [ $NUMREGRESS -ne 0 ] ; then
*** 164,174 ****
  fi

  # It passed.  Update the state.
- for LOG in $TESTLOGS ; do
-   L=`basename $LOG`
-   awk '/^PASS: / { print "'$L'",$2; }' $LOG || exit 1
- done | sort | uniq | comm -23 - $FAILED > ${PASSES}~ || exit 1
- [ -s ${PASSES}~ ] || exit 1
- mv ${PASSES}~ ${PASSES} || exit 1
  echo pass > $RESULT
  exit 0
--- 173,177 ----

brgds, H-P