https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63651
--- Comment #15 from Dominique d'Humieres <dominiq at lps dot ens.fr> ---
With the patch in comment 14, I get
=== obj-c++ Summary for unix/-m64 ===
# of expected passes 3073
# of unexpected failures 13
# of expected failures 19
# of unresolved testcases 8
# of unsupported tests 74
=== obj-c++ Summary ===
# of expected passes 6207
# of unexpected failures 24
# of expected failures 21
# of unresolved testcases 16
# of unsupported tests 142
and
=== objc Summary for unix/-m64 ===
# of expected passes 5939
# of unexpected failures 27
# of expected failures 6
# of unresolved testcases 10
# of unsupported tests 91
=== objc Summary ===
# of expected passes 12045
# of unexpected failures 43
# of expected failures 12
# of unresolved testcases 20
# of unsupported tests 176
The additional failures compared to the use of the 10.9 SDK are
FAIL: obj-c++.dg/torture/strings/const-cfstring-1.mm -O* -fnext-runtime
(test for excess errors)
FAIL: objc.dg/torture/strings/const-cfstring-1.m -O* -fnext-runtime (test
for excess errors)
FAIL: objc.dg/objc-foreach-4.m -fnext-runtime (test for excess errors)
FAIL: objc.dg/objc-foreach-5.m -fnext-runtime (test for excess errors)
Apparently they are related to the fact that NS_BLOCKS_AVAILABLE is no longer
checked.
