From: Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>
To: Andreas Schwab <schwab@suse.de>
Cc: Gerald Pfeifer <gerald@pfeifer.com>, Torsten Duwe <duwe@suse.de>,
"Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>,
Sandra Loosemore <sandra@codesourcery.com>,
Marek Polacek <polacek@redhat.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
Szabolcs Nagy <szabolcs.nagy@arm.com>,
nd@arm.com, Li Bin <huawei.libin@huawei.com>,
Jiri Kosina <jkosina@suse.cz>,
Marcus Shawcroft <Marcus.Shawcroft@arm.com>,
Takahiro Akashi <takahiro.akashi@linaro.org>,
Andrew Wafaa <Andrew.Wafaa@arm.com>
Subject: Re: [PATCH v12] add -fpatchable-function-entry=N,M option
Date: Tue, 01 Aug 2017 13:03:00 -0000 [thread overview]
Message-ID: <B3ACC0F7-B23C-428B-95BF-A5AA853C1208@linaro.org> (raw)
In-Reply-To: <mvm8tj3r24a.fsf@suse.de>
> On Aug 1, 2017, at 1:52 PM, Andreas Schwab <schwab@suse.de> wrote:
>
> On Aug 01 2017, Gerald Pfeifer <gerald@pfeifer.com> wrote:
>
>> On Mon, 31 Jul 2017, Maxim Kuvyrkov wrote:
>>> I don't see an easy way to correctly differentiate between "attribute"
>>> nops and "bundle" nops, so XFAILing these tests on ia64 seems like a
>>> valid approach.
>>
>> Make sense, given that the use of Itanium has gone done drastically.
>
> You can get the same failure with any target, for example if there are
> delay slots to be filled.
Andreas,
Do you know a reliable way of checking whether target can issue nops in simple code?
One alternative would be to apply testcase only to white-listed architectures, which is, imo, less preferable.
Regards,
--
Maxim Kuvyrkov
www.linaro.org
next prev parent reply other threads:[~2017-08-01 13:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-06 14:03 [PATCH v11] " Torsten Duwe
2017-07-07 13:58 ` Richard Earnshaw (lists)
2017-07-07 19:30 ` [PATCH v12] " Torsten Duwe
2017-07-17 12:10 ` Torsten Duwe
2017-07-20 10:58 ` Maxim Kuvyrkov
2017-07-20 12:06 ` Torsten Duwe
2017-07-20 13:12 ` Maxim Kuvyrkov
2017-07-25 7:16 ` Maxim Kuvyrkov
2017-07-25 8:07 ` Torsten Duwe
2017-07-25 13:03 ` Torsten Duwe
2017-07-26 14:16 ` Andreas Schwab
2017-07-26 14:26 ` Torsten Duwe
2017-07-26 14:33 ` Andreas Schwab
2017-07-31 11:47 ` Maxim Kuvyrkov
2017-08-01 10:43 ` Gerald Pfeifer
2017-08-01 10:53 ` Andreas Schwab
2017-08-01 13:03 ` Maxim Kuvyrkov [this message]
2017-08-01 13:36 ` Andreas Schwab
2017-08-11 12:42 ` [PATCH] skip patchable_function_entry tests on ia64 Torsten Duwe
2017-08-14 16:50 ` Jim Wilson
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=B3ACC0F7-B23C-428B-95BF-A5AA853C1208@linaro.org \
--to=maxim.kuvyrkov@linaro.org \
--cc=Andrew.Wafaa@arm.com \
--cc=Marcus.Shawcroft@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=duwe@suse.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=huawei.libin@huawei.com \
--cc=jkosina@suse.cz \
--cc=nd@arm.com \
--cc=polacek@redhat.com \
--cc=sandra@codesourcery.com \
--cc=schwab@suse.de \
--cc=szabolcs.nagy@arm.com \
--cc=takahiro.akashi@linaro.org \
/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).