Bug with egcs-1.0 on alpha-dec-osf3.2

[Jeffrey A Law]

  In message < 34B1C150.167E@cmis.CSIRO.AU >you write:
  > FAIL: gcc.c-torture/execute/complex-5.c execution,  -O0 
  > FAIL: gcc.c-torture/execute/complex-5.c execution,  -O1 
  > FAIL: gcc.c-torture/execute/complex-5.c execution,  -O2 
  > FAIL: gcc.c-torture/execute/complex-5.c execution,  -O2
These are normal on the alpha (and a few other platforms).  There's some fundamental
problems with GCC's complex type.  Hopefully someone will fix them soon.

  > FAIL: gcc.c-torture/execute/ieee/fp-cmp-1.c execution,  -O0 
  > FAIL: gcc.c-torture/execute/ieee/fp-cmp-1.c execution,  -O1 
  > FAIL: gcc.c-torture/execute/ieee/fp-cmp-1.c execution,  -O2 
  > FAIL: gcc.c-torture/execute/ieee/fp-cmp-1.c execution,  -O2
I believe this is actually a bug in the testing harness -- fp-cmp-1.c depends
on strict IEEE FP conformance, which the alpha does not do by default.  I
believe newer versions of the test harness are supposed to arrange for IEEE
complaint code on the Alpha.

  > FAIL: g++.benjamin/p12475.C  (test for warnings, line 4)
  > XPASS: g++.brendan/array1.C overflow in array dimension.* , (test for
  > errors, line 6)
  > XPASS: g++.jason/destruct3.C - (test for bogus messages, line 38)
  > XPASS: g++.law/profile1.C (test for excess errors)
  > XPASS: g++.law/profile1.C  Execution test
  > XPASS: g++.mike/dyncast1.C  Execution test
  > XPASS: g++.mike/dyncast2.C  Execution test
These look pretty typical too.

Thanks!

jeff