linux-mips
[Top] [All Lists]

Re: unresolved (soft)float symbols

To: Philippe De Swert <philippedeswert@scarlet.be>
Subject: Re: unresolved (soft)float symbols
From: Ralf Baechle <ralf@linux-mips.org>
Date: Thu, 13 Jan 2005 16:16:07 +0100
Cc: linux-mips <linux-mips@linux-mips.org>
In-reply-to: <IA9DY0$DCC07516FD959EE0729448D36856A324@scarlet.be>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <IA9DY0$DCC07516FD959EE0729448D36856A324@scarlet.be>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.4.1i
On Thu, Jan 13, 2005 at 03:08:24PM +0100, Philippe De Swert wrote:

> The module builds fine also, but when insmodding I get the following error.
> 
> insmod: unresolved symbol __fixdfsi
> insmod: unresolved symbol __floatsidf
> insmod: unresolved symbol __muldf3
> insmod: unresolved symbol __adddf3
> 
> As these are all float operations I am wondering about the following things:
> 
> 1.why they are in there? I have a soft-float toolchain....

That's why they are there.

> 2.Is there float support in the kernel? While googling for it I found a few

Nothing whatsoever.

> things talking about FP point in the kernel. Does it have something to do with
> the Algorithmics/MIPS FPU emulator. (Although it does not work emulator or
> not. Which I expected because it should only be used by apps which emit FPU
> calls, and this should not happen because I use a softfloat toolchain). So I
> expect it does not really have something to do with this.
> 3.I took care of using the same compiler options as the kernel compilation
> uses. I guess this is the correct way, and the problems are thus not related
> to this.

The simple answer is no FP in the kernel.

  Ralf

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