FYI: g++ FAILs from vendor nm for 3.0 20010305 on hppa2.0-hp-hpux10.20

[RDBrown@mira.net]

Native configuration is hppa2.0-hp-hpux10.20

		=== g++ Summary ===

# of expected passes		4591
# of unexpected failures	961
# of expected failures		942
# of untested testcases		19
/devel/span/rdb/src/gcc-20010305.obj/gcc/testsuite/../g++ version 3.0 20010305 (prerelease)

Looking at gcc/testsuite/g++.log it appears most of the unexpected failures
are from /usr/ccs/bin/nm core dumping when called from collect2.
A check-g++ using GNU nm has got past g++.dg/special/conpr-2.C and
g++.dg/special/conpr-3.C without problem. While I understand gas is no
longer mandatory, GNU nm may be needed on this platform.

bash-2.02$ pwd
/devel/span/rdb/src/gcc-20010305.obj/gcc/testsuite
bash-2.02$ fgrep -1 'Excess errors:' g++.log
FAIL: g++.dg/special/conpr-2.C (test for excess errors)
Excess errors:
collect2: /usr/ccs/bin/nm terminated with signal 11 [Segmentation fault]
--
FAIL: g++.dg/special/conpr-3.C (test for excess errors)
Excess errors:
collect2: /usr/ccs/bin/nm terminated with signal 11 [Segmentation fault]
--
FAIL: g++.dg/special/conpr-3.C (test for excess errors)
Excess errors:
collect2: /usr/ccs/bin/nm terminated with signal 11 [Segmentation fault]
bash-2.02$ what /usr/ccs/bin/nm
/usr/ccs/bin/nm:
	92453-07 command s800.sgs nm B.10.21 960821

bash-2.02$ fgrep collect2 g++.log | sort | uniq -c
 916 collect2: /usr/ccs/bin/nm terminated with signal 11 [Segmentation fault]
1834 collect2: /usr/ccs/bin/nm terminated with signal 11 [Segmentation fault]
  40 collect2: ld returned 1 exit status
  80 collect2: ld returned 1 exit status