From: Ralf Baechle <ralf@linux-mips.org>
To: Philippe De Swert <philippedeswert@scarlet.be>
Cc: linux-mips <linux-mips@linux-mips.org>
Subject: Re: unresolved (soft)float symbols
Date: Thu, 13 Jan 2005 16:16:07 +0100 [thread overview]
Message-ID: <20050113151607.GA23657@linux-mips.org> (raw)
In-Reply-To: <IA9DY0$DCC07516FD959EE0729448D36856A324@scarlet.be>
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
next prev parent reply other threads:[~2005-01-13 15:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 14:08 unresolved (soft)float symbols Philippe De Swert
2005-01-13 14:13 ` sjhill
2005-01-13 15:16 ` Ralf Baechle [this message]
2005-01-13 17:17 ` David Daney
-- strict thread matches above, loose matches on Subject: below --
2005-01-14 9:34 Philippe De Swert
2005-01-14 9:45 Philippe De Swert
2005-01-14 9:45 ` Philippe De Swert
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=20050113151607.GA23657@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=philippedeswert@scarlet.be \
/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