diff options
author | Ralf Corsepius <ralf.corsepius@rtems.org> | 2005-02-18 11:29:22 +0000 |
---|---|---|
committer | Ralf Corsepius <ralf.corsepius@rtems.org> | 2005-02-18 11:29:22 +0000 |
commit | 74e98074feb178e618a751cf0330b7f1be8c4bd4 (patch) | |
tree | 0e392679ed0ab67c81d7e71946fcbef70370d5c4 /cpukit/score/cpu/powerpc/rtems/old-exceptions/cpu.h | |
parent | 2005-02-18 Ralf Corsepius <ralf.corsepius@rtems.org> (diff) | |
download | rtems-74e98074feb178e618a751cf0330b7f1be8c4bd4.tar.bz2 |
(CPU_HARDWARE_FP, CPU_ALL_TASKS_ARE_FP,
CPU_IDLE_TASK_IS_FP): Remove.
Diffstat (limited to '')
-rw-r--r-- | cpukit/score/cpu/powerpc/rtems/old-exceptions/cpu.h | 47 |
1 files changed, 0 insertions, 47 deletions
diff --git a/cpukit/score/cpu/powerpc/rtems/old-exceptions/cpu.h b/cpukit/score/cpu/powerpc/rtems/old-exceptions/cpu.h index 38b40749d4..29fe9fa44b 100644 --- a/cpukit/score/cpu/powerpc/rtems/old-exceptions/cpu.h +++ b/cpukit/score/cpu/powerpc/rtems/old-exceptions/cpu.h @@ -117,53 +117,6 @@ typedef void ( *ppc_isr_entry )( int, struct CPU_Interrupt_frame * ); #define CPU_ISR_PASSES_FRAME_POINTER 1 /* - * Does the CPU have hardware floating point? - * - * If TRUE, then the RTEMS_FLOATING_POINT task attribute is supported. - * If FALSE, then the RTEMS_FLOATING_POINT task attribute is ignored. - * - * If there is a FP coprocessor such as the i387 or mc68881, then - * the answer is TRUE. - * - * The macro name "PPC_HAS_FPU" should be made CPU specific. - * It indicates whether or not this CPU model has FP support. For - * example, it would be possible to have an i386_nofp CPU model - * which set this to false to indicate that you have an i386 without - * an i387 and wish to leave floating point support out of RTEMS. - */ - -#if ( PPC_HAS_FPU == 1 ) -#define CPU_HARDWARE_FP TRUE -#else -#define CPU_HARDWARE_FP FALSE -#endif - -/* - * Are all tasks RTEMS_FLOATING_POINT tasks implicitly? - * - * If TRUE, then the RTEMS_FLOATING_POINT task attribute is assumed. - * If FALSE, then the RTEMS_FLOATING_POINT task attribute is followed. - * - * If CPU_HARDWARE_FP is FALSE, then this should be FALSE as well. - */ - -#define CPU_ALL_TASKS_ARE_FP FALSE - -/* - * Should the IDLE task have a floating point context? - * - * If TRUE, then the IDLE task is created as a RTEMS_FLOATING_POINT task - * and it has a floating point context which is switched in and out. - * If FALSE, then the IDLE task does not have a floating point context. - * - * Setting this to TRUE negatively impacts the time required to preempt - * the IDLE task from an interrupt because the floating point context - * must be saved as part of the preemption. - */ - -#define CPU_IDLE_TASK_IS_FP FALSE - -/* * Should the saving of the floating point registers be deferred * until a context switch is made to another different floating point * task? |