From: "H.J. Lu" <hongjiu.lu@intel.com>
To: gcc-patches@gcc.gnu.org
Subject: [x32] PATCH: Require ia32 instead of ilp32
Date: Fri, 27 May 2011 13:36:00 -0000 [thread overview]
Message-ID: <20110527123402.GA8453@intel.com> (raw)
Hi,
objc.dg/torture/forward-1.m is also expected to fail on x32. Checking
it in.
H.J.
---
commit cabf76cce0f4efcfdd3fb033255830c1336a0c64
Author: H.J. Lu <hjl.tools@gmail.com>
Date: Fri May 27 04:59:36 2011 -0700
Require ia32 instead of ilp32.
diff --git a/gcc/testsuite/ChangeLog.x32 b/gcc/testsuite/ChangeLog.x32
index 5c4728b..f82e95c 100644
--- a/gcc/testsuite/ChangeLog.x32
+++ b/gcc/testsuite/ChangeLog.x32
@@ -1,3 +1,7 @@
+2011-05-27 H.J. Lu <hongjiu.lu@intel.com>
+
+ * objc.dg/torture/forward-1.m: Require ia32 instead of ilp32.
+
2011-05-20 H.J. Lu <hongjiu.lu@intel.com>
PR target/48529
diff --git a/gcc/testsuite/objc.dg/torture/forward-1.m b/gcc/testsuite/objc.dg/torture/forward-1.m
index bccf4a1..b77ff28 100644
--- a/gcc/testsuite/objc.dg/torture/forward-1.m
+++ b/gcc/testsuite/objc.dg/torture/forward-1.m
@@ -1,6 +1,6 @@
/* { dg-do run } */
/* See if -forward::/-performv:: is able to work. */
-/* { dg-xfail-run-if "PR36610" { ! { { i?86-*-* x86_64-*-* } && ilp32 } } { "-fgnu-runtime" } { "" } } */
+/* { dg-xfail-run-if "PR36610" { ! { { i?86-*-* x86_64-*-* } && ia32 } } { "-fgnu-runtime" } { "" } } */
/* { dg-skip-if "Needs OBJC2 Implementation" { *-*-darwin* && { lp64 } } { "-fnext-runtime" } { "" } } */
/* There is no implementation of forward: in the NeXT m64 libobjc/Object
neither have we implemented this in our extensions - so we have to skip it
next reply other threads:[~2011-05-27 12:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 13:36 H.J. Lu [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-04 23:35 H.J. Lu
2011-04-25 4:19 H.J. Lu
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=20110527123402.GA8453@intel.com \
--to=hongjiu.lu@intel.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=hjl.tools@gmail.com \
/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).