From: Yvan Roux <yvan.roux@linaro.org>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Richard Earnshaw <Richard.Earnshaw@arm.com>,
Ramana Radhakrishnan <Ramana.Radhakrishnan@arm.com>,
Kyrylo Tkachov <kyrylo.tkachov@arm.com>
Subject: [PATCH, ARM] Fix testcases that require Thumb2 effective target.
Date: Mon, 04 May 2015 09:14:00 -0000 [thread overview]
Message-ID: <CAD57uCfWrN8LgcfMVBmW_ssx-MJwRLzsBJt_-yfuqYo+3K-1Gg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 466 bytes --]
Hi,
This patch fixes two ARM testcases that require target to be Thumb2
effective. One is built for Cortex-m3, the purpose of the second one
is to generate thumb2_addsi3_compare0_scratch insn and both are
failing when compiled for armv5t for instance.
Built and regtested, is it OK for trunk ?
Thanks,
Yvan
2015-05-04 Yvan Roux <yvan.roux@linaro.org>
* gcc.target/arm/pr65067.c: Require Thumb2 effective target.
* gcc.target/arm/pr65924.c: Likewise.
[-- Attachment #2: testsuite.diff --]
[-- Type: text/plain, Size: 734 bytes --]
diff --git a/gcc/testsuite/gcc.target/arm/pr65067.c b/gcc/testsuite/gcc.target/arm/pr65067.c
index 9ddd7bb..05da294 100644
--- a/gcc/testsuite/gcc.target/arm/pr65067.c
+++ b/gcc/testsuite/gcc.target/arm/pr65067.c
@@ -1,4 +1,5 @@
/* { dg-do compile } */
+/* { dg-require-effective-target arm_thumb2_ok } */
/* { dg-options "-mthumb -mcpu=cortex-m3 -O2" } */
struct tmp {
diff --git a/gcc/testsuite/gcc.target/arm/pr65924.c b/gcc/testsuite/gcc.target/arm/pr65924.c
index 746749f..e1ad394 100644
--- a/gcc/testsuite/gcc.target/arm/pr65924.c
+++ b/gcc/testsuite/gcc.target/arm/pr65924.c
@@ -1,4 +1,5 @@
/* { dg-do compile } */
+/* { dg-require-effective-target arm_thumb2_ok } */
/* { dg-options "-O2 -mthumb" } */
int a, b, c;
next reply other threads:[~2015-05-04 9:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-04 9:14 Yvan Roux [this message]
2015-05-05 8:16 ` Kyrill Tkachov
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=CAD57uCfWrN8LgcfMVBmW_ssx-MJwRLzsBJt_-yfuqYo+3K-1Gg@mail.gmail.com \
--to=yvan.roux@linaro.org \
--cc=Ramana.Radhakrishnan@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kyrylo.tkachov@arm.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).