linux-mips
[Top] [All Lists]

Re: unresolved symbol litodp,dptoli,dpmul - floating point operations in

To: Jun Sun <jsun@mvista.com>
Subject: Re: unresolved symbol litodp,dptoli,dpmul - floating point operations in kernel
From: Ralf Baechle <ralf@linux-mips.org>
Date: Mon, 13 Oct 2003 22:54:35 +0200
Cc: Geert Uytterhoeven <geert@linux-m68k.org>, durai <durai@isofttech.com>, mips <linux-mips@linux-mips.org>
In-reply-to: <20031010095824.B4192@mvista.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <02d001c38f36$ba4a8e00$6b00a8c0@DURAI> <Pine.GSO.4.21.0310101627400.8302-100000@waterleaf.sonytel.be> <20031010095824.B4192@mvista.com>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.4.1i
On Fri, Oct 10, 2003 at 09:58:24AM -0700, Jun Sun wrote:

> > > > insmod: unresolved symbol dptoli
> > > > insmod: unresolved symbol dpmul
> > > > insmod: unresolved symbol litodp

> If you are really really desparate, something like the following
> might work.
> 
> void use_fpu(void)
> {
>       if (is_fpu_owner()) {
>               save_fp(current);
>               loose_fpu();
>               enable_fpu();
>       }
>       local_irq_save(flags);
>       
>       /* now use fpu and store the results */
> 
>       local_irq_restore(flags);
> }
> 
> I like to emphsize this is just a hack and I am not even sure if it will work
> at all.  If compiler complains you might have to change the
> CC flag for that file or use fpu with inline assembly.

The symbols he was missing are used for software floating point.  Software
floating point in kernel space is perfectly ok since it doesn't use the FPU
so your hack isn't even needed.

  Ralf

<Prev in Thread] Current Thread [Next in Thread>