From: Tamar Christina <Tamar.Christina@arm.com>
To: GCC Patches <gcc-patches@gcc.gnu.org>
Cc: nd <nd@arm.com>, Christophe Lyon <christophe.lyon@linaro.org>,
"Kyrylo Tkachov" <Kyrylo.Tkachov@arm.com>,
Ramana Radhakrishnan <Ramana.Radhakrishnan@arm.com>,
Richard Earnshaw <Richard.Earnshaw@arm.com>
Subject: [GCC][PATCH][ARM] Require arm_arch_v8a_ok for sdiv_costs_1.c
Date: Tue, 13 Jun 2017 10:12:00 -0000 [thread overview]
Message-ID: <VI1PR0801MB2031461F4FC6FAF4C03E0C24FFC20@VI1PR0801MB2031.eurprd08.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 295 bytes --]
Hi All,
This fixes the failing test gcc.target/arm/sdiv_costs_1.c by
requiring arm_arch_v8a_ok.
OK for trunk?
gcc/testsuite/
2017-06-13 Tamar Christina <tamar.christina@arm.com>
* gcc.target/arm/sdiv_costs_1.c:
Require arm_arch_v8a_ok and add march option.
Thanks,
Tamar
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: sdiv-armv8.patch --]
[-- Type: text/x-patch; name="sdiv-armv8.patch", Size: 610 bytes --]
diff --git a/gcc/testsuite/gcc.target/arm/sdiv_costs_1.c b/gcc/testsuite/gcc.target/arm/sdiv_costs_1.c
index 3920590dfcce975aaf7cbe7a4d056df203b7ca2e..9d094ac0c1d12193e8db82120d266bae5b5bf297 100644
--- a/gcc/testsuite/gcc.target/arm/sdiv_costs_1.c
+++ b/gcc/testsuite/gcc.target/arm/sdiv_costs_1.c
@@ -1,6 +1,6 @@
/* { dg-do compile } */
-/* { dg-options "-O3" } */
-/* { dg-require-effective-target arm_v8_vfp_ok } */
+/* { dg-options "-O3 -march=armv8-a" } */
+/* { dg-require-effective-target arm_arch_v8a_ok } */
/* Both sdiv and udiv can be used here, so prefer udiv. */
int f1 (unsigned char *p)
next reply other threads:[~2017-06-13 10:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-13 10:12 Tamar Christina [this message]
2017-06-13 10:13 ` Kyrill Tkachov
2017-06-13 12:24 ` Christophe Lyon
2017-06-15 9:26 ` Tamar Christina
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=VI1PR0801MB2031461F4FC6FAF4C03E0C24FFC20@VI1PR0801MB2031.eurprd08.prod.outlook.com \
--to=tamar.christina@arm.com \
--cc=Kyrylo.Tkachov@arm.com \
--cc=Ramana.Radhakrishnan@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=christophe.lyon@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=nd@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).