From: Kyrill Tkachov <kyrylo.tkachov@arm.com>
To: Andreas Schwab <schwab@suse.de>
Cc: James Greenhalgh <James.Greenhalgh@arm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Marcus Shawcroft <Marcus.Shawcroft@arm.com>,
Richard Earnshaw <Richard.Earnshaw@arm.com>
Subject: Re: [PATCH][AArch64][12/14] Target attributes and target pragmas tests
Date: Wed, 05 Aug 2015 10:12:00 -0000 [thread overview]
Message-ID: <55C1E19E.1060800@arm.com> (raw)
In-Reply-To: <mvm1tfiumye.fsf@hawking.suse.de>
On 05/08/15 10:03, Andreas Schwab wrote:
> Kyrill Tkachov <kyrylo.tkachov@arm.com> writes:
>
>> diff --git a/gcc/testsuite/gcc.target/aarch64/target_attr_1.c b/gcc/testsuite/gcc.target/aarch64/target_attr_1.c
>> new file mode 100644
>> index 0000000..72d0838
>> --- /dev/null
>> +++ b/gcc/testsuite/gcc.target/aarch64/target_attr_1.c
>> @@ -0,0 +1,12 @@
>> +/* { dg-do assemble } */
>> +/* { dg-options "-O2 -mcpu=thunderx -save-temps" } */
>> +
>> +__attribute__ ((target ("cpu=cortex-a72.cortex-a53")))
>> +int
>> +foo (int a)
>> +{
>> + return a + 1;
>> +}
>> +
>> +/* { dg-final { scan-assembler "//.tune cortex-a72.cortex-a53" } } */
>> +/* { dg-final { scan-assembler-not "thunderx" } } */
> FAIL: gcc.target/aarch64/target_attr_1.c (test for excess errors)
> Excess errors:
> Assembler messages:
> Error: unknown cpu `thunderx'
> Error: unrecognized option -mcpu=thunderx
yeah, that happens if your assembler doesn't support -mcpu=thunderx.
Newer binutils should support it.
Kyrill
>
> Andreas.
>
next prev parent reply other threads:[~2015-08-05 10:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-16 15:21 Kyrill Tkachov
2015-07-21 17:15 ` James Greenhalgh
2015-07-24 8:43 ` Kyrill Tkachov
2015-08-03 11:32 ` James Greenhalgh
2015-08-05 14:52 ` James Greenhalgh
2015-08-05 9:03 ` Andreas Schwab
2015-08-05 10:12 ` Kyrill Tkachov [this message]
2015-08-05 14:27 ` Andreas Schwab
2015-08-05 14:34 ` 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=55C1E19E.1060800@arm.com \
--to=kyrylo.tkachov@arm.com \
--cc=James.Greenhalgh@arm.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=schwab@suse.de \
/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).