public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kyrill Tkachov <kyrylo.tkachov@foss.arm.com>
To: Stam Markianos-Wright <stam.markianos-wright@arm.com>,
	"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: "nickc@redhat.com" <nickc@redhat.com>,
	Ramana Radhakrishnan <Ramana.Radhakrishnan@arm.com>,
	Richard Earnshaw <Richard.Earnshaw@arm.com>
Subject: Re: [PING][PATCH][GCC][ARM] Arm generates out of range conditional branches in Thumb2 (PR91816)
Date: Thu, 30 Jan 2020 15:21:00 -0000	[thread overview]
Message-ID: <e1f940d5-f7bd-74f6-1dd9-18f4cb8acc08@foss.arm.com> (raw)
In-Reply-To: <36c9c580-2b73-c780-656b-5bce51af464a@arm.com>


On 1/30/20 2:42 PM, Stam Markianos-Wright wrote:
>
>
> On 1/28/20 10:35 AM, Kyrill Tkachov wrote:
>> Hi Stam,
>>
>> On 1/8/20 3:18 PM, Stam Markianos-Wright wrote:
>>>
>>> On 12/10/19 5:03 PM, Kyrill Tkachov wrote:
>>>> Hi Stam,
>>>>
>>>> On 11/15/19 5:26 PM, Stam Markianos-Wright wrote:
>>>>> Pinging with more correct maintainers this time :)
>>>>>
>>>>> Also would need to backport to gcc7,8,9, but need to get this 
>>>>> approved
>>>>> first!
>>>>>
>>>> Sorry for the delay.
>>> Same here now! Sorry totally forget about this in the lead up to Xmas!
>>>
>>> Done the changes marked below and also removed the unnecessary extra 
>>> #defines
>>> from the test.
>>
>>
>> This is ok with a nit on the testcase...
>>
>>
>> diff --git a/gcc/testsuite/gcc.target/arm/pr91816.c 
>> b/gcc/testsuite/gcc.target/arm/pr91816.c
>> new file mode 100644
>> index 
>> 0000000000000000000000000000000000000000..757c897e9c0db32709227b3fdf1b4a8033428232
>> --- /dev/null
>> +++ b/gcc/testsuite/gcc.target/arm/pr91816.c
>> @@ -0,0 +1,61 @@
>> +/* { dg-do compile } */
>> +/* { dg-options "-march=armv7-a -mthumb -mfpu=vfpv3-d16" }  */
>> +int printf(const char *, ...);
>> +
>>
>> I think this needs a couple of effective target checks like 
>> arm_hard_vfp_ok and arm_thumb2_ok. See other tests in gcc.target/arm 
>> that add -mthumb to the options.
>
> Hmm, looking back at this now, is there any reason why it can't just be:
>
> /* { dg-do compile } */
> /* { dg-require-effective-target arm_thumb2_ok } */
> /* { dg-additional-options "-mthumb" }  */
>
> were we don't override the march or fpu options at all, but just use 
> `require-effective-target arm_thumb2_ok` to make sure that thumb2 is 
> supported?
>
> The attached new diff does just that.
>

Works for me, there are plenty of configurations run with fpu that it 
should get the right coverage.

Ok (make sure commit the updated, if needed, ChangeLog as well)

Thanks!

Kyrill


> Cheers :)
>
> Stam.
>
>>
>> Thanks,
>> Kyrill
>>
>

  reply	other threads:[~2020-01-30 14:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-11 14:57 [PATCH][GCC][ARM] " Stam Markianos-Wright
2019-10-13 15:37 ` Ramana Radhakrishnan
2019-10-21  9:40   ` Stam Markianos-Wright
2019-11-15 17:27     ` [PING][PATCH][GCC][ARM] " Stam Markianos-Wright
2019-12-02 16:43       ` Stam Markianos-Wright
2019-12-09 17:50         ` Stam Markianos-Wright
2019-12-10 17:03       ` Kyrill Tkachov
2020-01-08 15:19         ` Stam Markianos-Wright
2020-01-16 16:30           ` Stam Markianos-Wright
2020-01-27 16:28             ` [PINGx2][PATCH][GCC][ARM] " Stam Markianos-Wright
2020-01-28 11:05           ` [PING][PATCH][GCC][ARM] " Kyrill Tkachov
2020-01-30 14:55             ` Stam Markianos-Wright
2020-01-30 15:21               ` Kyrill Tkachov [this message]
2020-03-04 14:15                 ` Tamar Christina
2020-03-04 14:18                   ` 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=e1f940d5-f7bd-74f6-1dd9-18f4cb8acc08@foss.arm.com \
    --to=kyrylo.tkachov@foss.arm.com \
    --cc=Ramana.Radhakrishnan@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=nickc@redhat.com \
    --cc=stam.markianos-wright@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).