cvs commit: src/sys/powerpc/fpu fpu_add.c fpu_arith.h fpu_compare.c fpu_div.c fpu_emu.c fpu_emu.h fpu_explode.c fpu_extern.h fpu_implode.c fpu_instr.h fpu_mul.c fpu_sqrt.c fpu_subr.c

[M. Warner Losh]

In message: <20080224063836.GB42714 at zim.MIT.EDU>
            David Schultz <das at FreeBSD.org> writes:
: On Sat, Feb 23, 2008, Marcel Moolenaar wrote:
: > marcel      2008-02-23 20:05:27 UTC
: > 
: >   FreeBSD src repository
: > 
: >   Added files:
: >     sys/powerpc/fpu      fpu_add.c fpu_arith.h fpu_compare.c 
: >                          fpu_div.c fpu_emu.c fpu_emu.h 
: >                          fpu_explode.c fpu_extern.h fpu_implode.c 
: >                          fpu_instr.h fpu_mul.c fpu_sqrt.c 
: >                          fpu_subr.c 
: >   Log:
: >   Add a floating-point emulator so that a single userland or single ABI
: >   can run on processors that don't have a FPU. This is typically the
: >   case for Book E processors. While a tuned system will probably want
: >   to use soft-float (or use a processor that has a FPU if the usage is
: >   FP intensive enough), allowing hard-float on FPU-less systems gives
: >   great portability and flexibility.
: >   
: >   Obtained from: NetBSD
: 
: It looks like everything except for fpu_emu.? and fpu_instr.h is
: pretty generic, and surely there are other architectures (e.g.,
: ARM, low-power 486-SX clones) that could use in-kernel FP emulation.
: Do you think it's worthwhile to separate the MI bits and put them
: somewhere other than sys/powerpc, or is the plan to burn that
: bridge when we get to it?

I'd say the first new architecture to want to use this (ARM, 486SX or
MIPS) should pay the freight for that.

Warner