From: Bob Doyle <doyle@primenet.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: PowerPC function returning long long
Date: Wed, 13 Oct 1999 04:54:31 +0000 [thread overview]
Message-ID: <38041087.62AB190@primenet.com> (raw)
I was playing with the inline assembler and the ppc
timebase facility and created the following function -
unsigned long long get_timebase(void) {
unsigned long tbu;
unsigned long tbl;
unsigned long junk;
__asm__ __volatile__ ("
1: mftbu %2
mftb %1
mftbu %0
cmpw %0,%2
bne 1b"
: "=r" (tbu), "=r" (tbl), "=r" (junk));
return ((unsigned long long)tbu << 32) | tbl;
}
This function compiles to (gcc 2.95.1) :
get_timebase:
1: mftbu 5
mftb 6
mftbu 0
cmpw 0,5
bne 1b
mr 10,0
li 9,0
mr 7,10
mr 12,6
li 8,0
li 11,0
or 3,7,11
or 4,8,12
blr
As one can see, most of this is a bunch of register thrashing.
I expected it to generate something along this:
1: mftbu 5
mftb 4
mftbu 3
cmpw 3,4
bne 1b
blr
I assume it is because gcc is struggling with the code
in the return statement.
Is there a better way to write the return statement?
Is there a register constraint for a long long register
(like the "A" constraint for the x86 which returns the
64 bit data in edx:eax)?
Any ideas?
Yes I know that there is a similar function in
arch/ppc/kernel/apus_setup.c which isn't quite
what I want.
Bob
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~1999-10-13 4:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-13 4:54 Bob Doyle [this message]
1999-10-13 8:06 ` PowerPC function returning long long Gabriel Paubert
1999-10-13 12:27 ` Michael Meissner
1999-10-14 4:12 ` Bob Doyle
1999-10-14 4:35 ` Michael Meissner
1999-10-14 7:28 ` [TANGENT] GNU as [was: Re: PowerPC function returning long long] Bill Brooks
1999-10-14 12:45 ` Daniel Jacobowitz
1999-10-14 13:21 ` Michael Meissner
1999-10-14 12:44 ` PowerPC function returning long long Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
1999-10-13 6:14 Christophe Lizzi
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=38041087.62AB190@primenet.com \
--to=doyle@primenet.com \
--cc=linuxppc-dev@lists.linuxppc.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).