public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Christophe Lyon <christophe.lyon@linaro.org>
To: Christian Bruel <christian.bruel@st.com>
Cc: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>,
		"kyrylo.tkachov@arm.com" <kyrylo.tkachov@arm.com>,
		"Ramana.Radhakrishnan@arm.com" <Ramana.Radhakrishnan@arm.com>,
		"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, ARM]: Fix static interworking call
Date: Wed, 23 Sep 2015 22:09:00 -0000	[thread overview]
Message-ID: <CAKdteOY1-aFu83tFZm7ZC2KB0UvkMRYaj0i6vhrzDPTg059qUg@mail.gmail.com> (raw)
In-Reply-To: <56001104.5070307@st.com>

On 21 September 2015 at 16:15, Christian Bruel <christian.bruel@st.com> wrote:
>
>
> On 09/18/2015 05:03 PM, Richard Earnshaw wrote:
>
>>> Index: attr_thumb-static2.c
>>> ===================================================================
>>> --- attr_thumb-static2.c        (revision 227904)
>>> +++ attr_thumb-static2.c        (working copy)
>>> @@ -1,6 +1,6 @@
>>>   /* Check that interwork between static functions is correctly resolved.
>>> */
>>>
>>> -/* { dg-skip-if "" { ! { arm_thumb1_ok || arm_thumb2_ok } } } */
>>> +/* { dg-require-effective-target arm_thumb2_ok } */
>>>   /* { dg-options "-O0 -march=armv7-a -mfloat-abi=hard" } */
>>>   /* { dg-do compile } */
>>>
>>>
>>
>> Do you really need -mfloat-abi=hard for this test?  If so, I think you
>> also need "dg-require-effective-target arm_hard_vfp_ok".  See
>> gcc.target/arm/pr65729.c
>>
>
> The test was not crashing for -mfloat-abi=soft.
> But the number of blx is independent. So yes we can write the conditions in
> such a way the test runs without hard fp.
>
> is this one better ?

You need to move the dg-do directive before the other ones (otherwise,
it overrides the effect of require-target).

      reply	other threads:[~2015-09-23 21:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-17  8:54 Christian Bruel
2015-09-17  9:13 ` Kyrill Tkachov
2015-09-18 14:26 ` Richard Earnshaw
2015-09-18 14:51   ` Christian Bruel
2015-09-18 15:14     ` Richard Earnshaw
2015-09-21  0:22       ` Christophe Lyon
2015-09-21 10:57         ` Christian Bruel
2015-09-21 14:01           ` Christophe Lyon
2015-09-21 14:16       ` Christian Bruel
2015-09-23 22:09         ` Christophe Lyon [this message]

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=CAKdteOY1-aFu83tFZm7ZC2KB0UvkMRYaj0i6vhrzDPTg059qUg@mail.gmail.com \
    --to=christophe.lyon@linaro.org \
    --cc=Ramana.Radhakrishnan@arm.com \
    --cc=Richard.Earnshaw@foss.arm.com \
    --cc=christian.bruel@st.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).