From: David Woodhouse <dwmw2@infradead.org>
To: Kyle McMartin <kyle@ubuntu.com>
Cc: linuxppc-dev@ozlabs.org, Meelis Roos <mroos@linux.ee>,
paulus@samba.org,
Linux Kernel list <linux-kernel@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: V4L2: __ucmpdi2 undefined on ppc
Date: Sun, 17 Dec 2006 13:29:05 +0000 [thread overview]
Message-ID: <1166362145.6714.53.camel@pmac.infradead.org> (raw)
In-Reply-To: <20061214195842.GA14041@athena.road.mcmartin.ca>
On Thu, 2006-12-14 at 14:58 -0500, Kyle McMartin wrote:
> I posted a patch to Paul this week to fix this,
Hm, I didn't see it on linuxppc-dev.
> Since ppc32 can't do a 64bit comparison on its own it seems, gcc
> will generate a call to a helper function from libgcc. What other
> arches do is link libgcc.a into libs-y, and export the symbol
> they want from it.
You still get to 'accidentally' do 64-bit arithmetic in-kernel that way
though. Might be better just to provide __ucmpdi2, just as we have for
the other functions which are required from libgcc
It'd be better just to fix the compiler though -- which is in fact what
they've done: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25724
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21237
I've applied this as a temporary hack to the Fedora kernel until the
compiler is updated there...
--- linux-2.6.19.ppc/arch/powerpc/kernel/misc_32.S~ 2006-11-29 21:57:37.000000000 +0000
+++ linux-2.6.19.ppc/arch/powerpc/kernel/misc_32.S 2006-12-17 12:19:48.000000000 +0000
@@ -728,6 +728,27 @@ _GLOBAL(__lshrdi3)
or r4,r4,r7 # LSW |= t2
blr
+/*
+ * __ucmpdi2: 64-bit comparison
+ *
+ * R3/R4 has 64 bit value A
+ * R5/R6 has 64 bit value B
+ * result in R3: 0 for A < B
+ * 1 for A == B
+ * 2 for A > B
+ */
+_GLOBAL(__ucmpdi2)
+ cmplw r7,r3,r5 # compare high words
+ li r3,0
+ blt r7,2f # a < b ... return 0
+ bgt r7,1f # a > b ... return 2
+ cmplw r6,r4,r6 # compare low words
+ blt r6,2f # a < b ... return 0
+ li r3,1
+ ble r6,2f # a = b ... return 1
+1: li r3,2
+2: blr
+
_GLOBAL(abs)
srawi r4,r3,31
xor r3,r3,r4
--- linux-2.6.19.ppc/arch/powerpc/kernel/ppc_ksyms.c~ 2006-12-15 17:19:56.000000000 +0000
+++ linux-2.6.19.ppc/arch/powerpc/kernel/ppc_ksyms.c 2006-12-17 12:16:54.000000000 +0000
@@ -161,9 +161,11 @@ EXPORT_SYMBOL(to_tm);
long long __ashrdi3(long long, int);
long long __ashldi3(long long, int);
long long __lshrdi3(long long, int);
+int __ucmpdi2(uint64_t, uint64_t);
EXPORT_SYMBOL(__ashrdi3);
EXPORT_SYMBOL(__ashldi3);
EXPORT_SYMBOL(__lshrdi3);
+EXPORT_SYMBOL(__ucmpdi2);
#endif
EXPORT_SYMBOL(memcpy);
--
dwmw2
next parent reply other threads:[~2006-12-17 13:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.SOC.4.61.0612131359430.10721@math.ut.ee>
[not found] ` <1166053317.909.19.camel@praia>
[not found] ` <20061214195842.GA14041@athena.road.mcmartin.ca>
2006-12-17 13:29 ` David Woodhouse [this message]
2008-02-06 14:39 ` V4L2: __ucmpdi2 undefined on ppc Stephane Marchesin
2008-03-02 18:48 ` Stephane Marchesin
2008-03-02 21:53 ` Segher Boessenkool
2008-03-04 16:37 ` David Woodhouse
2008-03-04 16:58 ` Scott Wood
2008-03-04 20:32 ` Segher Boessenkool
2008-03-04 21:44 ` Paul Mackerras
2008-03-04 21:47 ` Scott Wood
2008-03-04 22:43 ` 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=1166362145.6714.53.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=kyle@ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mchehab@infradead.org \
--cc=mroos@linux.ee \
--cc=paulus@samba.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).