From: Janis Johnson <janis_johnson@mentor.com>
To: Christophe Lyon <christophe.lyon@linaro.org>, <janisjo@codesourcery.com>
Cc: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [testsuite patch] add code to arm_thumbX_ok to exercise ABI
Date: Mon, 18 Aug 2014 15:33:00 -0000 [thread overview]
Message-ID: <53F21CC8.1020309@mentor.com> (raw)
In-Reply-To: <CAKdteOb_ak47+RqdV6nRA48anvz3dLYX-b-Zeg3C1-tAFhjhjQ@mail.gmail.com>
On 08/18/2014 07:36 AM, Christophe Lyon wrote:
> On 8 August 2014 02:30, Janis Johnson <janis_johnson@mentor.com> wrote:
>> Running an arm-none-eabi test that adds "-mthumb" for a multilib that
>> uses "-march=armv5te -mfloat-abi=hard" works fine if the test doesn't
>> have any calls, but if it does then the effective-target checks for
>> arm_thumb1_ok and arm_thumb2_ok pass but the test's compile step fails
>> with "sorry, unimplemented: Thumb-1 hard-float VFP ABI".
>>
>> This patch adds code to those effective-target checks to exercise
>> argument handling and causes them to fail for the multilib flags
>> listed above. Tested by running gcc.target/arm tests with a variety
>> of multilib flags. OK for mainline and the 4.9 branch?
>>
>> Janis
>
> Some time ago (https://gcc.gnu.org/ml/gcc-patches/2012-09/msg01501.html)
> I suggested to add similar stuff to check_effective_target_arm_arch_FUNC_ok
> for similar reasons.
>
> Do you agree?
>
I agree but I prefer to have one of the ARM maintainers approve changes
like that; we sometimes have different philosophies about how to handle
additional options in tests.
Janis
prev parent reply other threads:[~2014-08-18 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 0:30 Janis Johnson
2014-08-08 10:40 ` Richard Earnshaw
2014-08-18 14:36 ` Christophe Lyon
2014-08-18 15:33 ` Janis Johnson [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=53F21CC8.1020309@mentor.com \
--to=janis_johnson@mentor.com \
--cc=christophe.lyon@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=janisjo@codesourcery.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).