Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Joe deBlaquiere <jadb@redhat.com>
To: Jun Sun <jsun@mvista.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
	"Maciej W. Rozycki" <macro@ds2.pg.gda.pl>,
	Florian Lohoff <flo@rfc822.org>,
	linux-mips@oss.sgi.com, ralf@oss.sgi.com
Subject: Re: NON FPU cpus - way to go
Date: Wed, 07 Feb 2001 14:43:52 -0600	[thread overview]
Message-ID: <3A81B388.1090806@redhat.com> (raw)
In-Reply-To: 3A81A3DC.E75E6045@mvista.com



Jun Sun wrote:

> Alan Cox wrote:
> 
>>>  The i386 way seems reasonable, IMHO.  Have a configure option to enable
>>> an FPU emulator.  Panic upon boot if no FP hardware is available and no
>>> emulator is compiled in.
>> 
>> Its an interesting question whether it belongs in the kernel or libc.
>> Discuss ;)
>> 
> 
> 
> I favor the libc approach as it is faster.

You can still compile in the FP emulator just 'in case'... That way you 
leave it up to the application as to whether to do be quick or cheap. 
This also ensures binary portability (well, mostly, there's always .so 
ABI issues and the like...)

> 
> Unfortunately I don't think glibc for MIPS can be configured with
> --without-fp.  I modified a patch to get glibc 2.0.6 working for no-fp config,
> but it is not a clean one.  Is anybody working on that for the latest glibc
> 2.2?
> 
> 

AFAIK, 2.0.7-20 (from Jay Carlson), 2.1.95 (from SGI), 2.2, and the 
current CVS can all be configured for soft float.

>> Also we missed a trick on the x86 and I want to fix that one day, which is
>> to have an __fpu ELF segment so if you boot an FPU emu kernel on an fpu
>> box you regain 47K
> 
> 
> Ironically for MIPS you MUST have the FPU emulater when the CPU actually has a
> FPU. :-)
> 

I'm confused here... why is this?



-- 
Joe

  reply	other threads:[~2001-02-07 20:49 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-07 13:48 NON FPU cpus - way to go Florian Lohoff
2001-02-07 16:36 ` Maciej W. Rozycki
2001-02-07 16:59   ` Florian Lohoff
2001-02-07 18:19     ` Maciej W. Rozycki
2001-02-07 18:53   ` Alan Cox
2001-02-07 18:53     ` Alan Cox
2001-02-07 19:37     ` Jun Sun
2001-02-07 20:43       ` Joe deBlaquiere [this message]
2001-02-08  8:45         ` Geert Uytterhoeven
2001-02-08 10:13       ` Maciej W. Rozycki
2001-02-08 10:52         ` Kevin D. Kissell
2001-02-08 10:52           ` Kevin D. Kissell
2001-02-08 11:19           ` Maciej W. Rozycki
2001-02-08 11:38             ` Kevin D. Kissell
2001-02-08 11:38               ` Kevin D. Kissell
2001-02-08 12:05               ` Maciej W. Rozycki
2001-02-08 10:42     ` Maciej W. Rozycki
2001-02-08 10:53       ` Geert Uytterhoeven
2001-02-08 10:58         ` Alan Cox
2001-02-08 10:58           ` Alan Cox
2001-02-08 11:05           ` Geert Uytterhoeven
2001-02-08 11:22         ` Maciej W. Rozycki
2001-02-07 19:01 ` Jun Sun
2001-02-07 22:51   ` Kevin D. Kissell
2001-02-07 22:51     ` Kevin D. Kissell
2001-02-08 10:54     ` Maciej W. Rozycki
2001-02-08 10:24   ` Maciej W. Rozycki
2001-09-20  3:13 ` NON FPU cpus (again) Atsushi Nemoto
2001-09-20  3:16   ` Ralf Baechle
2001-09-20  4:02     ` Atsushi Nemoto

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=3A81B388.1090806@redhat.com \
    --to=jadb@redhat.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=flo@rfc822.org \
    --cc=jsun@mvista.com \
    --cc=linux-mips@oss.sgi.com \
    --cc=macro@ds2.pg.gda.pl \
    --cc=ralf@oss.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