From: Jeremy Kerr <jk@ozlabs.org>
To: linuxppc-dev@ozlabs.org
Cc: Kevin Diggs <kevdig@hypersurf.com>
Subject: Re: inline assembly & r0 SOS
Date: Wed, 6 Aug 2008 10:41:50 +1000 [thread overview]
Message-ID: <200808061041.50577.jk@ozlabs.org> (raw)
In-Reply-To: <4898EE60.9080206@hypersurf.com>
Hi Kevin,
> /*
> * Turn r3 (range) into a rotate count for the selected
> range. * 0 -> 23, 1 -> 31
> */
> __asm__ __volatile__ ( "slwi %0,%0,3\n"
> "addi %0,%0,23\n"
> "rlwnm %0,%1,%0,30,31\n":
> "=r"(ret):
> "r"(config),"0"(range)
> );
Wouldn't this be much simpler in plain C?
However, if you really do need to do this in inline asm, you can use
the "b" modifier rather than "r" to avoid using r0.
Cheers,
Jeremy
next prev parent reply other threads:[~2008-08-06 0:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 0:20 inline assembly & r0 SOS Kevin Diggs
2008-08-06 0:35 ` Benjamin Herrenschmidt
2008-08-06 0:41 ` Jeremy Kerr [this message]
2008-08-06 2:31 ` Kevin Diggs
2008-08-06 8:49 ` Andreas Schwab
2008-08-06 14:39 ` Segher Boessenkool
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=200808061041.50577.jk@ozlabs.org \
--to=jk@ozlabs.org \
--cc=kevdig@hypersurf.com \
--cc=linuxppc-dev@ozlabs.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).