From: Conn Clark <clark@esteem.com>
To: Dan Kegel <dkegel@ixiacom.com>,
May Ling List <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: What problems are there with floating point emulation in the kernel?
Date: Wed, 22 May 2002 15:41:25 -0700 [thread overview]
Message-ID: <3CEC1E95.4CCCA5CA@esteem.com> (raw)
In-Reply-To: 9A9C83C019F35D47A570460E87D5D8AB0125EAB9@racerx.ixiacom.com
Dan Kegel wrote:
>
> Since it's very easy to avoid the use of floating point in
> the kernel, it has not been a big issue.
>
> Do you need to use floating point in the kernel for some reason?
> - Dan
Its not the use of floating point in the kernel thats the problem.
I would like to "emulate" the fpu in the kernel so I can
compile glibc and everything else with fpu instructions to save
ram. I have been told however that there are "issues" with this
approach, and the only way to go is to emulate the fpu in the
kernel and compile everything with soft float. What I want to
know is what these issues are? (accuracy,segment_fault,etc..)
Conn
--
*****************************************************************
If you live at home long enough, your parents will move out.
*****************************************************************
Conn Clark
Engineering Stooge clark@esteem.com
Electronic Systems Technology Inc. www.esteem.com
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-05-22 22:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-22 19:27 What problems are there with floating point emulation in the kernel? Dan Kegel
2002-05-22 22:41 ` Conn Clark [this message]
2002-05-22 22:52 ` Dan Kegel
-- strict thread matches above, loose matches on Subject: below --
2002-05-22 22:57 Rosen Jeremy
2002-04-24 16:56 Conn Clark
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=3CEC1E95.4CCCA5CA@esteem.com \
--to=clark@esteem.com \
--cc=dkegel@ixiacom.com \
--cc=linuxppc-embedded@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).