From: "Jay Carlson" <nop@nop.com>
To: "Dominic Sweetman" <dom@algor.co.uk>,
"Bradley D. LaRonde" <brad@ltc.com>
Cc: "Andrew R. Baker" <andrewb@uab.edu>,
"Linux SGI" <linux@cthulhu.engr.sgi.com>, <linux-mips@fnet.fr>,
<linux-mips@vger.rutgers.edu>
Subject: Re: FP emulation patch available
Date: Tue, 7 Mar 2000 07:08:23 -0500 [thread overview]
Message-ID: <578601bf882d$d945f650$0a00000a@decoy> (raw)
In-Reply-To: 200003071022.KAA00275@gladsmuir.algor.co.uk
> Bradley D. LaRonde (brad@ltc.com) writes (re the FPA emulator out of
> Algorithmics via Kevin Kissell):
>
> > I would jump right on this but I really need it for 2.3.47+.
>
> It's good to see our donation to the Linux project being taken up
> enthusiastically , but didn't SGI have some code like this? I mean,
> you can't have a serious MIPS run-time system without an FP emulator,
> can you?
quoting from softftp.S from 2.3.19:
* For now it's just a crude hack good enough to run certain fp programs
like
* Mozilla.
It's just dealing with denorms, NaNs, etc as inputs. AFAIK NetBSD was no
better until pretty recently.
Whether Linux or NetBSD, as systems, were ever serious MIPS run-time
systems---well, you wrote the book, so I'm inclined to get out of the
argument.
>From my LinuxCE perspective, a full FP emu is fairly important for getting
binary compatibility back with mainline Linux/MIPS---we've been in the
softfp ghetto. But most of what we do with FP is, uh, keep /bin/df happy
when it tries to calculate the percentage of free disk space, and the like.
And dropping softfp means we don't *have* to maintain a forked
toolchain/libc.
(of course, getting rid of softfp makes mips16 more...interesting...)
Jay
WARNING: multiple messages have this Message-ID (diff)
From: "Jay Carlson" <nop@nop.com>
To: Dominic Sweetman <dom@algor.co.uk>, "Bradley D. LaRonde" <brad@ltc.com>
Cc: "Andrew R. Baker" <andrewb@uab.edu>,
Linux SGI <linux@cthulhu.engr.sgi.com>,
linux-mips@fnet.fr, linux-mips@vger.rutgers.edu
Subject: Re: FP emulation patch available
Date: Tue, 7 Mar 2000 07:08:23 -0500 [thread overview]
Message-ID: <578601bf882d$d945f650$0a00000a@decoy> (raw)
Message-ID: <20000307120823.Q5F9l8fyUYl0aky-UZm3K5vUqpWr8HGi82eLJWqO_vM@z> (raw)
In-Reply-To: 200003071022.KAA00275@gladsmuir.algor.co.uk
> Bradley D. LaRonde (brad@ltc.com) writes (re the FPA emulator out of
> Algorithmics via Kevin Kissell):
>
> > I would jump right on this but I really need it for 2.3.47+.
>
> It's good to see our donation to the Linux project being taken up
> enthusiastically , but didn't SGI have some code like this? I mean,
> you can't have a serious MIPS run-time system without an FP emulator,
> can you?
quoting from softftp.S from 2.3.19:
* For now it's just a crude hack good enough to run certain fp programs
like
* Mozilla.
It's just dealing with denorms, NaNs, etc as inputs. AFAIK NetBSD was no
better until pretty recently.
Whether Linux or NetBSD, as systems, were ever serious MIPS run-time
systems---well, you wrote the book, so I'm inclined to get out of the
argument.
From my LinuxCE perspective, a full FP emu is fairly important for getting
binary compatibility back with mainline Linux/MIPS---we've been in the
softfp ghetto. But most of what we do with FP is, uh, keep /bin/df happy
when it tries to calculate the percentage of free disk space, and the like.
And dropping softfp means we don't *have* to maintain a forked
toolchain/libc.
(of course, getting rid of softfp makes mips16 more...interesting...)
Jay
next prev parent reply other threads:[~2000-03-07 12:23 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-07 4:12 FP emulation patch available Andrew R. Baker
[not found] ` <097a01bf87eb$ebe4d4d0$b8119526@ltc.com>
[not found] ` <200003071022.KAA00275@gladsmuir.algor.co.uk>
2000-03-07 12:08 ` Jay Carlson [this message]
2000-03-07 12:08 ` Jay Carlson
2000-03-08 16:25 ` Ralf Baechle
2000-03-08 16:18 ` Ralf Baechle
[not found] ` <38C4C328.9656C68E@niisi.msk.ru>
2000-03-07 18:54 ` Andrew R. Baker
2000-03-07 19:43 ` Harald Koerfgen
2000-03-08 16:11 ` Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
2000-03-08 9:43 Kevin D. Kissell
2000-03-08 9:43 ` Kevin D. Kissell
2000-03-08 17:02 ` Richard van den Berg
2000-03-08 18:43 ` Harald Koerfgen
2000-03-08 20:12 Kevin D. Kissell
2000-03-08 20:12 ` Kevin D. Kissell
2000-03-09 2:03 ` Warner Losh
[not found] ` <200003082223.WAA00605@gladsmuir.algor.co.uk>
2000-03-09 2:13 ` Warner Losh
2000-03-09 20:20 ` Harald Koerfgen
2000-03-12 13:03 Kevin D. Kissell
2000-03-12 13:03 ` Kevin D. Kissell
2000-03-12 21:23 ` Harald Koerfgen
2000-03-12 21:52 Kevin D. Kissell
2000-03-12 21:52 ` Kevin D. Kissell
2000-03-13 22:22 ` Harald Koerfgen
2000-03-13 8:33 Kevin D. Kissell
2000-03-13 8:33 ` Kevin D. Kissell
2000-03-13 13:46 ` Alan Cox
2000-03-13 13:46 ` Alan Cox
2000-03-13 19:05 ` Harald Koerfgen
2000-03-13 19:05 ` Harald Koerfgen
2000-03-13 17:46 ` Ralf Baechle
2000-03-13 20:13 ` William J. Earl
2000-03-14 18:50 ` Andrew R. Baker
[not found] ` <200003142317.XAA00644@gladsmuir.algor.co.uk>
2000-03-15 14:35 ` Kevin D. Kissell
2000-03-13 23:20 Kevin D. Kissell
2000-03-13 23:20 ` Kevin D. Kissell
2000-03-14 18:15 ` Harald Koerfgen
2000-03-21 22:27 Kevin D. Kissell
2000-03-21 22:27 ` Kevin D. Kissell
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='578601bf882d$d945f650$0a00000a@decoy' \
--to=nop@nop.com \
--cc=andrewb@uab.edu \
--cc=brad@ltc.com \
--cc=dom@algor.co.uk \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@vger.rutgers.edu \
--cc=linux@cthulhu.engr.sgi.com \
/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