From: Kyrill Tkachov <kyrylo.tkachov@arm.com>
To: Ramana Radhakrishnan <ramana.radhakrishnan@arm.com>,
Shiva Chen <shiva0217@gmail.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
"nickc@redhat.com" <nickc@redhat.com>,
Richard Earnshaw <Richard.Earnshaw@arm.com>
Subject: Re: [GCC, ARM] armv8 linux toolchain asan testcase fail due to stl missing conditional code
Date: Wed, 03 Jun 2015 08:53:00 -0000 [thread overview]
Message-ID: <556EBC77.3060601@arm.com> (raw)
In-Reply-To: <556EBBAC.2020504@arm.com>
On 03/06/15 09:32, Ramana Radhakrishnan wrote:
>> This pattern is not predicable though, i.e. it doesn't have the "predicable" attribute set to "yes".
>> Therefore the compiler should be trying to branch around here rather than try to do a cond_exec.
>> Why does the generated code above look like it's converted to conditional execution?
>> Could you produce a self-contained reduced testcase for this?
> CCFSM state machine in ARM state.
>
> arm.c (final_prescan_insn).
Ah ok.
This patch makes sense then.
As Ramana mentioned, please mark the pattern with "predicable" and also set the "predicable_short_it" attribute to "no" so that it will not be conditionalised in Thumb2 mode or when -mrestrict-it is enabled.
Thanks,
Kyrill
>
> Ramana
>
>> Thanks,
>> Kyrill
>>
>>> @@ -91,9 +91,9 @@
>>> {
>>> enum memmodel model = memmodel_from_int (INTVAL (operands[2]));
>>> if (is_mm_relaxed (model) || is_mm_consume (model) || is_mm_acquire (model))
>>> - return \"str<sync_sfx>\t%1, %0\";
>>> + return \"str<sync_sfx>%?\t%1, %0\";
>>> else
>>> - return \"stl<sync_sfx>\t%1, %0\";
>>> + return \"stl<sync_sfx>%?\t%1, %0\";
>>> }
>>> )
>>>
next prev parent reply other threads:[~2015-06-03 8:36 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 5:27 Shiva Chen
2015-06-03 8:31 ` Ramana Radhakrishnan
2015-06-03 8:36 ` Kyrill Tkachov
[not found] ` <556EBBAC.2020504@arm.com>
2015-06-03 8:53 ` Kyrill Tkachov [this message]
2015-06-03 9:33 ` Shiva Chen
2015-06-04 4:51 ` Shiva Chen
2015-06-04 8:24 ` Kyrill Tkachov
2015-06-04 8:42 ` Richard Earnshaw
2015-06-04 10:01 ` Shiva Chen
2015-06-04 10:04 ` Kyrill Tkachov
2015-06-05 8:34 ` Shiva Chen
2015-06-05 8:35 ` Kyrill Tkachov
2015-06-05 10:59 ` Shiva Chen
2015-06-05 13:11 ` Kyrill Tkachov
2015-06-05 13:14 ` Richard Earnshaw
2015-06-05 14:02 ` Kyrill Tkachov
2015-06-09 8:44 ` Kyrill Tkachov
2015-09-30 17:10 ` Kyrill Tkachov
2015-10-01 9:10 ` Kyrill Tkachov
2015-10-01 20:21 ` Christophe Lyon
2015-10-02 12:57 ` 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=556EBC77.3060601@arm.com \
--to=kyrylo.tkachov@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nickc@redhat.com \
--cc=ramana.radhakrishnan@arm.com \
--cc=shiva0217@gmail.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).