Re: PING *objc, NeXT runtime, testsuite changes*

[dominiq at lps dot ens dot fr (Dominique Dhumieres)]

> Looks like one extra fail on each of m32 and m64 ...

With -m32 the failures are:

FAIL: obj-c++.dg/bitfield-3.mm -fgnu-runtime execution test
FAIL: obj-c++.dg/objc-gc-3.mm -fgnu-runtime (internal compiler error)
FAIL: obj-c++.dg/objc-gc-3.mm -fgnu-runtime (test for excess errors)
FAIL: obj-c++.dg/stubify-1.mm -fgnu-runtime (test for excess errors)
FAIL: obj-c++.dg/stubify-2.mm -fgnu-runtime (test for excess errors)
FAIL: obj-c++.dg/const-str-9.mm -fnext-runtime (test for excess errors)
FAIL: obj-c++.dg/cxx-ivars-3.mm -fnext-runtime (test for excess errors)
FAIL: obj-c++.dg/stubify-1.mm -fnext-runtime (test for excess errors)
FAIL: obj-c++.dg/stubify-2.mm -fnext-runtime (test for excess errors)

On powerpc-apple-darwin9 revision 156774 with the last patch for
PR43061, I get:

=== objc Summary for unix/-m64 ===

# of expected passes		2373
# of unexpected failures	89
# of expected failures		46
# of unresolved testcases	1
# of unsupported tests		28

=== objc Summary ===

# of expected passes		6051
# of unexpected failures	111
# of expected failures		71
# of unresolved testcases	2
# of unsupported tests		52
/opt/gcc/darwin_buildw/gcc/xgcc  version 4.5.0 20100215 (experimental) [trunk revision 156774p1] (GCC) 

=== obj-c++ Summary for unix/-m64 ===

# of expected passes		859
# of unexpected failures	20
# of unexpected successes	4
# of expected failures		50
# of unresolved testcases	3
# of unsupported tests		8

=== obj-c++ Summary ===

# of expected passes		1769
# of unexpected failures	26
# of unexpected successes	11
# of expected failures		63
# of unresolved testcases	6
# of unsupported tests		16
/opt/gcc/darwin_buildw/gcc/testsuite/obj-c++/../../g++  version 4.5.0 20100215 (experimental) [trunk revision 156774p1] (GCC) 

i.e., more failures of objc and less for obj-c++ compared to
x86_64-apple-darwin10.

Dominique