public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "dominiq at lps dot ens.fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/63651] Lot of failures in obj(c|-c++) with yosemite Date: Sat, 20 Dec 2014 10:54:00 -0000 [thread overview] Message-ID: <bug-63651-4-kaqkd1OzQ1@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-63651-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63651 --- Comment #10 from Dominique d'Humieres <dominiq at lps dot ens.fr> --- If I replace the files /usr/include/objc/NSObject.h and /System/Library/Frameworks/Foundation.framework/Headers/NSString.h with the corresponding files from /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/ The errors reduce to === obj-c++ tests === Running target unix/-m32 FAIL: obj-c++.dg/cxx-ivars-3.mm -fnext-runtime execution test FAIL: obj-c++.dg/gnu-api-2-objc.mm -fnext-runtime execution test === obj-c++ Summary for unix/-m32 === # of expected passes 3151 # of unexpected failures 2 # of expected failures 2 # of unsupported tests 68 Running target unix/-m64 FAIL: obj-c++.dg/gnu-api-2-objc.mm -fnext-runtime execution test FAIL: obj-c++.dg/isa-field-1.mm -fnext-runtime (test for excess errors) FAIL: obj-c++.dg/try-catch-2.mm -fnext-runtime execution test FAIL: obj-c++.dg/try-catch-9.mm -fnext-runtime execution test === obj-c++ Summary for unix/-m64 === # of expected passes 3090 # of unexpected failures 4 # of expected failures 19 # of unsupported tests 74 === obj-c++ Summary === # of expected passes 6241 # of unexpected failures 6 # of expected failures 21 # of unsupported tests 142 /opt/gcc/p_build/gcc/testsuite/obj-c++/../../xg++ version 5.0.0 20141219 (experimental) [trunk revision 218883p2] (GCC) === objc tests === Running target unix/-m32 FAIL: objc.dg/call-super-2.m -fnext-runtime (test for warnings, line 104) FAIL: objc.dg/call-super-2.m -fnext-runtime (test for warnings, line 74) FAIL: objc.dg/gnu-api-2-objc.m -fnext-runtime execution test FAIL: objc.dg/ivar-scope-4.m -fnext-runtime execution test FAIL: objc.dg/objc-foreach-4.m -fnext-runtime (test for excess errors) UNRESOLVED: objc.dg/objc-foreach-4.m -fnext-runtime compilation failed to produce executable UNRESOLVED: objc.dg/objc-foreach-5.m -fnext-runtime scan-assembler _addStuffUp: FAIL: objc.dg/objc-foreach-5.m -fnext-runtime (test for excess errors) === objc Summary for unix/-m32 === # of expected passes 6124 # of unexpected failures 6 # of expected failures 6 # of unresolved testcases 2 # of unsupported tests 85 Running target unix/-m64 FAIL: objc.dg/call-super-2.m -fnext-runtime (test for warnings, line 104) FAIL: objc.dg/call-super-2.m -fnext-runtime (test for warnings, line 74) FAIL: objc.dg/exceptions-2.m -fnext-runtime execution test FAIL: objc.dg/gnu-api-2-objc.m -fnext-runtime execution test FAIL: objc.dg/isa-field-1.m -fnext-runtime (test for excess errors) FAIL: objc.dg/objc-foreach-4.m -fnext-runtime (test for excess errors) UNRESOLVED: objc.dg/objc-foreach-4.m -fnext-runtime compilation failed to produce executable UNRESOLVED: objc.dg/objc-foreach-5.m -fnext-runtime scan-assembler _addStuffUp: FAIL: objc.dg/objc-foreach-5.m -fnext-runtime (test for excess errors) FAIL: objc.dg/torture/forward-1.m -O0 -fnext-runtime execution test FAIL: objc.dg/torture/forward-1.m -O1 -fnext-runtime execution test FAIL: objc.dg/torture/forward-1.m -O2 -fnext-runtime execution test FAIL: objc.dg/torture/forward-1.m -O2 -flto -fnext-runtime execution test FAIL: objc.dg/torture/forward-1.m -O2 -flto -flto-partition=none -fnext-runtime execution test FAIL: objc.dg/torture/forward-1.m -O3 -fomit-frame-pointer -fnext-runtime execution test FAIL: objc.dg/torture/forward-1.m -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions -fnext-runtime execution test FAIL: objc.dg/torture/forward-1.m -O3 -fomit-frame-pointer -funroll-loops -fnext-runtime execution test FAIL: objc.dg/torture/forward-1.m -O3 -g -fnext-runtime execution test FAIL: objc.dg/torture/forward-1.m -Os -fnext-runtime execution test === objc Summary for unix/-m64 === # of expected passes 5957 # of unexpected failures 17 # of expected failures 6 # of unresolved testcases 2 # of unsupported tests 91 === objc Summary === # of expected passes 12081 # of unexpected failures 23 # of expected failures 12 # of unresolved testcases 4 # of unsupported tests 176 /opt/gcc/p_build/gcc/xgcc version 5.0.0 20141219 (experimental) [trunk revision 218883p2] (GCC) The new failures compared to darwin13 are FAIL: obj-c++.dg/isa-field-1.mm -fnext-runtime (test for excess errors) with -m64, FAIL: objc.dg/objc-foreach-4.m -fnext-runtime (test for excess errors) UNRESOLVED: objc.dg/objc-foreach-4.m -fnext-runtime compilation failed to produce executable UNRESOLVED: objc.dg/objc-foreach-5.m -fnext-runtime scan-assembler _addStuffUp: FAIL: objc.dg/objc-foreach-5.m -fnext-runtime (test for excess errors) with -m32, and FAIL: objc.dg/isa-field-1.m -fnext-runtime (test for excess errors) FAIL: objc.dg/objc-foreach-4.m -fnext-runtime (test for excess errors) UNRESOLVED: objc.dg/objc-foreach-4.m -fnext-runtime compilation failed to produce executable UNRESOLVED: objc.dg/objc-foreach-5.m -fnext-runtime scan-assembler _addStuffUp: FAIL: objc.dg/objc-foreach-5.m -fnext-runtime (test for excess errors) FAIL: objc.dg/torture/forward-1.m -O0 -fnext-runtime execution test FAIL: objc.dg/torture/forward-1.m -O1 -fnext-runtime execution test FAIL: objc.dg/torture/forward-1.m -O2 -fnext-runtime execution test FAIL: objc.dg/torture/forward-1.m -O2 -flto -fnext-runtime execution test FAIL: objc.dg/torture/forward-1.m -O2 -flto -flto-partition=none -fnext-runtime execution test FAIL: objc.dg/torture/forward-1.m -O3 -fomit-frame-pointer -fnext-runtime execution test FAIL: objc.dg/torture/forward-1.m -O3 -fomit-frame-pointer -funroll-all-loops -finline-functions -fnext-runtime execution test FAIL: objc.dg/torture/forward-1.m -O3 -fomit-frame-pointer -funroll-loops -fnext-runtime execution test FAIL: objc.dg/torture/forward-1.m -O3 -g -fnext-runtime execution test FAIL: objc.dg/torture/forward-1.m -Os -fnext-runtime execution test with -m64. The errors for are of the kind objc[1436]: -[Forwarder display]: unrecognized selector sent to instance 0x7f9ce9d04f30 (no message forward handler is installed) Is there a canonical way to force obj(c|-c++) to use the include files in /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.9.sdk/ instead of the native files in /usr and /System? Note that some remaining errors will go away if the same is used for /System/Library/Frameworks/Foundation.framework/Headers/NSArray.h.
next prev parent reply other threads:[~2014-12-20 10:54 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-63651-4@http.gcc.gnu.org/bugzilla/> 2014-11-01 11:52 ` fxcoudert at gcc dot gnu.org 2014-11-07 23:02 ` fxcoudert at gcc dot gnu.org 2014-11-08 13:45 ` dominiq at lps dot ens.fr 2014-11-08 13:53 ` fxcoudert at gcc dot gnu.org 2014-11-08 14:07 ` iains at gcc dot gnu.org 2014-11-08 14:09 ` howarth at bromo dot med.uc.edu 2014-11-08 14:22 ` howarth at bromo dot med.uc.edu 2014-11-20 19:27 ` egall at gwmail dot gwu.edu 2014-11-20 19:47 ` howarth at bromo dot med.uc.edu 2014-12-20 10:54 ` dominiq at lps dot ens.fr [this message] 2014-12-20 12:44 ` dominiq at lps dot ens.fr 2014-12-20 16:12 ` fxcoudert at gcc dot gnu.org 2014-12-20 16:18 ` iains at gcc dot gnu.org 2014-12-22 10:18 ` iains at gcc dot gnu.org 2014-12-22 14:17 ` dominiq at lps dot ens.fr 2014-12-22 21:29 ` mrs at gcc dot gnu.org 2014-12-22 21:49 ` iains at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-63651-4-kaqkd1OzQ1@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).