From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/6] ARM: prefetch: remove redundant "cc" clobber
Date: Wed, 24 Jul 2013 17:35:31 +0100 [thread overview]
Message-ID: <20130724163530.GV11072@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <alpine.LFD.2.03.1307241205050.15022@syhkavp.arg>
On Wed, Jul 24, 2013 at 05:16:59PM +0100, Nicolas Pitre wrote:
> On Wed, 24 Jul 2013, Will Deacon wrote:
> > On Tue, Jul 23, 2013 at 08:48:11PM +0100, Nicolas Pitre wrote:
> > > You know the legacy reason why the cc clobber was there, right?
> > > It certainly doesn't apply anymore.
> >
> > I was under the impression that it was due to ancient GCC behaviour and the "cc"
> > was there to prevent re-ordering. For interest, what are the specifics?
>
> In the old days, you had to take care of the predicate for conditional
> instructions in your inline asm code. So for example, if you had:
>
> if (foo)
> inline asm ("mov %0, #1" : "=r" (bar));
>
> That wouldn't work most of the time because even if the if condition was
> false, gcc would not branch over the inline asm code but expect you to
> take care of the condition code. That means the above needed to be
> written as:
>
> if (foo)
> inline asm ("mov%? %0, #1" : "=r" (bar));
>
> Because having %? added all over the place was cumbersome, the
> alternative was to add "cc" to the clobber list so gcc would then branch
> across the inline asm when the condition is false.
>
> But of course many people forgot about those subtle details quite often,
> and then gcc was changed so inline asm was made non predicated.
Holy sh*t....
Next time I complain to the tools guys about inline asm, I'll count my
blessings so they don't try and resurrect anything as horrendous as what
you've just described.
Thanks for the insight!
Will
next prev parent reply other threads:[~2013-07-24 16:35 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 11:36 [PATCH 0/6] Add support for pldw instruction on v7 MP cores Will Deacon
2013-07-23 11:36 ` [PATCH 1/6] ARM: prefetch: remove redundant "cc" clobber Will Deacon
2013-07-23 19:48 ` Nicolas Pitre
2013-07-24 10:19 ` Will Deacon
2013-07-24 16:16 ` Nicolas Pitre
2013-07-24 16:35 ` Will Deacon [this message]
2013-07-24 16:58 ` Russell King - ARM Linux
2013-07-24 17:22 ` Nicolas Pitre
2013-07-23 11:36 ` [PATCH 2/6] ARM: smp_on_up: move inline asm ALT_SMP patching macro out of spinlock.h Will Deacon
2013-07-23 19:55 ` Nicolas Pitre
2013-07-23 11:36 ` [PATCH 3/6] ARM: prefetch: add support for prefetchw using pldw on SMP ARMv7+ CPUs Will Deacon
2013-07-23 20:05 ` Nicolas Pitre
2013-07-24 10:42 ` Will Deacon
2013-07-23 11:36 ` [PATCH 4/6] ARM: locks: prefetch the destination word for write prior to strex Will Deacon
2013-07-23 20:10 ` Nicolas Pitre
2013-07-24 11:18 ` Will Deacon
2013-07-25 17:31 ` Stephen Boyd
2013-07-25 17:37 ` Stephen Boyd
2013-07-25 17:45 ` Will Deacon
2013-07-25 17:48 ` Will Deacon
2013-07-25 17:55 ` Stephen Boyd
2013-07-25 18:05 ` Will Deacon
2013-07-25 18:22 ` Stephen Boyd
2013-07-25 20:24 ` Nicolas Pitre
2013-07-26 10:34 ` Will Deacon
2013-07-26 14:46 ` Nicolas Pitre
2013-07-23 11:36 ` [PATCH 5/6] ARM: atomics: " Will Deacon
2013-07-23 20:12 ` Nicolas Pitre
2013-07-23 11:36 ` [PATCH 6/6] ARM: bitops: " Will Deacon
2013-07-23 20:15 ` Nicolas Pitre
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=20130724163530.GV11072@mudshark.cambridge.arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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 NNTP newsgroup(s).