public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Yvan Roux <yvan.roux@linaro.org>
To: Ramana Radhakrishnan <ramrad01@arm.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
	Vladimir Makarov <vmakarov@redhat.com>,
	Terry Guo <terry.guo@arm.com>,
		gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: patch to fix PR65648
Date: Tue, 14 Apr 2015 08:32:00 -0000	[thread overview]
Message-ID: <CAD57uCdgY=32LGDNGXQVOUp05poUC=RFJYxzTmXubpuFOEjCPw@mail.gmail.com> (raw)
In-Reply-To: <CAJA7tRZh968b4usdsY025jek-Va2nnw1J6aFvKGq8wKtbhOHeQ@mail.gmail.com>

On 14 April 2015 at 10:19, Ramana Radhakrishnan
<ramana.gcc@googlemail.com> wrote:
> On Thu, Apr 9, 2015 at 12:10 PM, Yvan Roux <yvan.roux@linaro.org> wrote:
>> Hi
>>
>> On 7 April 2015 at 22:02, Yvan Roux <yvan.roux@linaro.org> wrote:
>>> On 7 April 2015 at 21:33, Jakub Jelinek <jakub@redhat.com> wrote:
>>>> On Tue, Apr 07, 2015 at 09:28:51PM +0200, Yvan Roux wrote:
>>>>> validation is ongoing, but here is my attempt to add this testcase,
>>>>> does it look correct (it's the first time I use that kind of include
>>>>> in testsuite)
>>>>
>>>> The intent is that we have a testcase for all targets at various
>>>> optimization levels, plus one with specific options for the particular
>>>> target.
>>>> If you get at least one FAIL with this patch with Vlad's patch reverted and
>>>> no FAILs with that patch, the patch is ok for trunk with the obvious
>>>> ChangeLog entry.
>>
>> As this testcase needs to be executed, we can have some conflict at
>> link time, depending on how the libs were compiled. Here is what I've
>> for the moment, let me know if it's ok and/or if you have suggestion
>> on how to improve it.
>>
>> - armv6 doesn't support the hard-float ABI in Thumb mode, I disable
>> the testcase with this directive, but not sure it's the best way:
>> { dg-skip-if "avoid conflicting multilib options" { *-*-*eabihf } {
>> "*" } { "" } }ot
>>
>> - The original problem was reported on armv6-m arch. but is not
>> related to the M profile, if we stick to armv6-m the link will fail on
>> compiler which default to the -A profile.  As my guess is that -A
>> profile is more widely tested, I changed the -march flag to armv6. Do
>> you think it's ok ?
>
> IMO there are enough folks who test M profile. I'd drop all the arch
> specific options and just apply the patch.

The issue is more related to armv6 than M profile, but if it is widely
tested as well I can just commit the torture test if it's ok for
Jakub.

Thanks,
Yvan

> Thanks,
> Ramana
>
>>
>> With the attached patch there is only 1 FAIL before Vlad's patch on
>> the execution of the test and they all PASS when testing
>> arm-linux-gnueabi, and the target test is UNSUPPORTED when test
>> arm-linux-gnueabihf.
>>
>> Cheers,
>> Yvan
>>
>> 2105-04-09  Yvan Roux  <yvan.roux@linaro.org>
>>
>>         PR target/65648
>>         * gcc.c-torture/execute/pr65648.c: New test.
>>         * gcc.target/arm/pr65648.c: New test.

  reply	other threads:[~2015-04-14  8:32 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-07 15:02 Vladimir Makarov
2015-04-07 15:04 ` Jakub Jelinek
2015-04-07 15:52 ` Jakub Jelinek
2015-04-07 19:28   ` Yvan Roux
2015-04-07 19:33     ` Jakub Jelinek
2015-04-07 20:02       ` Yvan Roux
2015-04-09 11:10         ` Yvan Roux
2015-04-09 11:16           ` Jakub Jelinek
2015-04-13 13:42           ` Kyrill Tkachov
2015-04-13 14:11             ` Yvan Roux
2015-04-13 14:36               ` Kyrill Tkachov
2015-04-13 14:37                 ` Jakub Jelinek
2015-04-14  8:19           ` Ramana Radhakrishnan
2015-04-14  8:32             ` Yvan Roux [this message]
2015-04-14  8:33               ` Jakub Jelinek
2015-04-14  8:35                 ` Ramana Radhakrishnan
2015-04-14  9:14                   ` Yvan Roux

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='CAD57uCdgY=32LGDNGXQVOUp05poUC=RFJYxzTmXubpuFOEjCPw@mail.gmail.com' \
    --to=yvan.roux@linaro.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=ramrad01@arm.com \
    --cc=terry.guo@arm.com \
    --cc=vmakarov@redhat.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).