Searched hist:176491 (Results 1 - 13 of 13) sorted by relevance
| /freebsd-10.1-release/sys/powerpc/fpu/ | ||
| H A D | fpu_arith.h | 176491 Sat Feb 23 18:05:26 MST 2008 marcel 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 |
| H A D | fpu_compare.c | 176491 Sat Feb 23 18:05:26 MST 2008 marcel 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 |
| H A D | fpu_div.c | 176491 Sat Feb 23 18:05:26 MST 2008 marcel 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 |
| H A D | fpu_emu.h | 176491 Sat Feb 23 18:05:26 MST 2008 marcel 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 |
| H A D | fpu_implode.c | 176491 Sat Feb 23 18:05:26 MST 2008 marcel 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 |
| H A D | fpu_instr.h | 176491 Sat Feb 23 18:05:26 MST 2008 marcel 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 |
| H A D | fpu_mul.c | 176491 Sat Feb 23 18:05:26 MST 2008 marcel 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 |
| H A D | fpu_add.c | 176491 Sat Feb 23 18:05:26 MST 2008 marcel 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 |
| H A D | fpu_explode.c | 176491 Sat Feb 23 18:05:26 MST 2008 marcel 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 |
| H A D | fpu_extern.h | 176491 Sat Feb 23 18:05:26 MST 2008 marcel 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 |
| H A D | fpu_sqrt.c | 176491 Sat Feb 23 18:05:26 MST 2008 marcel 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 |
| H A D | fpu_subr.c | 176491 Sat Feb 23 18:05:26 MST 2008 marcel 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 |
| H A D | fpu_emu.c | 176491 Sat Feb 23 18:05:26 MST 2008 marcel 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 |
Completed in 72 milliseconds