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 tree-optimization/53708] New: [4.8 Regression] Many failures of the objc tests with -O3 -fnext-runtime and -m32
Date: Sun, 17 Jun 2012 13:29:00 -0000 [thread overview]
Message-ID: <bug-53708-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53708
Bug #: 53708
Summary: [4.8 Regression] Many failures of the objc tests with
-O3 -fnext-runtime and -m32
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: dominiq@lps.ens.fr
CC: iains@gcc.gnu.org, rguenth@gcc.gnu.org
Host: *-apple-darwin*
Target: *-apple-darwin*
Build: *-apple-darwin*
Between revisions 188187 (OK) and 188246 over one hundred tests failed with
-m32 and -O3 -fnext-runtime on *-apple-darwin*:
Running target unix/-m32
FAIL: objc/execute/exceptions/catchall-1.m compilation, -O3
-fomit-frame-pointer -fnext-runtime
UNRESOLVED: objc/execute/exceptions/catchall-1.m execution, -O3
-fomit-frame-pointer -fnext-runtime
FAIL: objc/execute/exceptions/catchall-1.m compilation, -O3 -g -fnext-runtime
UNRESOLVED: objc/execute/exceptions/catchall-1.m execution, -O3 -g
-fnext-runtime
FAIL: objc/execute/exceptions/finally-1.m compilation, -O3
-fomit-frame-pointer -fnext-runtime
UNRESOLVED: objc/execute/exceptions/finally-1.m execution, -O3
-fomit-frame-pointer -fnext-runtime
FAIL: objc/execute/exceptions/finally-1.m compilation, -O3 -g -fnext-runtime
...
FAIL: objc.dg/torture/tls/thr-init-3.m -O3 -fomit-frame-pointer
-fnext-runtime (test for excess errors)
WARNING: objc.dg/torture/tls/thr-init-3.m -O3 -fomit-frame-pointer
-fnext-runtime compilation failed to produce executable
FAIL: objc.dg/torture/tls/thr-init-3.m -O3 -g -fnext-runtime (test for excess
errors)
WARNING: objc.dg/torture/tls/thr-init-3.m -O3 -g -fnext-runtime compilation
failed to produce executable
=== objc Summary for unix/-m32 ===
# of expected passes 5891
# of unexpected failures 104
# of expected failures 6
# of unresolved testcases 92
# of unsupported tests 85
On x86_64-apple-darwin10 I also see the following failures with -m64
Running target unix/-m64
FAIL: objc/execute/formal_protocol-4.m compilation, -O3 -fomit-frame-pointer
-fnext-runtime
UNRESOLVED: objc/execute/formal_protocol-4.m execution, -O3
-fomit-frame-pointer -fnext-runtime
FAIL: objc/execute/formal_protocol-4.m compilation, -O3 -g -fnext-runtime
UNRESOLVED: objc/execute/formal_protocol-4.m execution, -O3 -g -fnext-runtime
FAIL: objc/execute/protocol-isEqual-2.m execution, -O3 -fomit-frame-pointer
-fnext-runtime
FAIL: objc/execute/protocol-isEqual-2.m execution, -O3 -g -fnext-runtime
=== objc Summary for unix/-m64 ===
# of expected passes 6045
# of unexpected failures 4
# of expected failures 14
# of unresolved testcases 2
# of unsupported tests 91
while on powerpc-apple-darwin9 I only see the execution failures. The
compilation failures are all of the kind
ld: in /var/tmp//ccVsf9ME.o, S_LITERAL_POINTERS section __OBJC,__message_refs
missing relocs
collect2: error: ld returned 1 exit status
They disappear if I compile the tests with '-O3 -fno-tree-vectorize', but
reappear with '-O2 -ftree-vectorize'.
According to Iain Sandoe, this is due to revisions 188235/188243.
next reply other threads:[~2012-06-17 13:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-17 13:29 dominiq at lps dot ens.fr [this message]
2012-06-17 14:13 ` [Bug tree-optimization/53708] " iains at gcc dot gnu.org
2012-06-18 8:52 ` [Bug middle-end/53708] " rguenth at gcc dot gnu.org
2012-06-18 10:00 ` dominiq at lps dot ens.fr
2012-06-18 12:42 ` dominiq at lps dot ens.fr
2012-06-18 20:11 ` iains at gcc dot gnu.org
2012-06-19 8:47 ` dominiq at lps dot ens.fr
2012-06-19 9:19 ` rguenth at gcc dot gnu.org
2012-06-19 9:21 ` rguenth at gcc dot gnu.org
2012-10-30 15:48 ` bergner at gcc dot gnu.org
2012-10-30 17:11 ` rguenther at suse dot de
2012-10-30 18:27 ` bergner at gcc dot gnu.org
2012-10-30 18:38 ` jakub at gcc dot gnu.org
2012-10-31 15:33 ` law at redhat dot com
2012-11-01 2:48 ` bergner at gcc dot gnu.org
2012-11-03 14:02 ` bergner at gcc dot gnu.org
2012-11-03 14:06 ` bergner 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-53708-4@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: link
Be 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).