From: Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>
To: Thomas Preudhomme <thomas.preudhomme@foss.arm.com>,
gcc-patches@gcc.gnu.org,
Ramana Radhakrishnan <Ramana.Radhakrishnan@arm.com>
Subject: Re: [PATCH, testsuite/ARM] Skip pr70496.c for cortex-m devices
Date: Wed, 06 Apr 2016 11:09:00 -0000 [thread overview]
Message-ID: <5704EE65.6070705@foss.arm.com> (raw)
In-Reply-To: <6491652.xk5pjihgLD@e108577-lin>
Hi Thomas,
On 06/04/16 12:03, Thomas Preudhomme wrote:
> Hi,
>
> Testcase in gcc.target/arm/pr70496.c uses an .arm directive so assumes the
> target has an ARM execution state. This patch adds a dg-skip-if directive to
> skip that test on Cortex-M targets since they don't have such an execution
> state.
>
> ChangeLog entry is as follows:
>
>
> *** gcc/testsuite/ChangeLog ***
>
> 2016-04-06 Thomas Preud'homme <thomas.preudhomme@arm.com>
>
> PR testsuite/70553
> * gcc.target/arm/pr70496.c: Skip for ARM Cortex-M targets.
>
>
> diff --git a/gcc/testsuite/gcc.target/arm/pr70496.c
> b/gcc/testsuite/gcc.target/arm/pr70496.c
> index
> 89957e2c7a75cb89153b3e3fc34d8051b6a997d1..548a8243059ddaec63ed897dc67f4751d806a065
> 100644
> --- a/gcc/testsuite/gcc.target/arm/pr70496.c
> +++ b/gcc/testsuite/gcc.target/arm/pr70496.c
> @@ -1,6 +1,7 @@
> /* { dg-do assemble } */
> /* { dg-options "-mthumb -O2" } */
> /* { dg-require-effective-target arm_thumb2_ok } */
> +/* { dg-skip-if "does not have ARM state" { arm_cortex_m } } */
>
Would it be better to just require the arm_arm_ok effective target?
That should try to compile a test with -marm added to the command,
which should fail for Cortex-M targets.
Thanks,
Kyrill
> int i;
> void
>
>
>
>
> Is this ok for trunk?
>
> Best regards,
>
> Thomas
>
next prev parent reply other threads:[~2016-04-06 11:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 11:04 Thomas Preudhomme
2016-04-06 11:09 ` Kyrill Tkachov [this message]
2016-04-07 16:13 ` Thomas Preudhomme
2016-04-07 16:14 ` Kyrill Tkachov
2016-04-06 11:16 ` Ramana Radhakrishnan
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=5704EE65.6070705@foss.arm.com \
--to=kyrylo.tkachov@foss.arm.com \
--cc=Ramana.Radhakrishnan@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=thomas.preudhomme@foss.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).