diff options
Diffstat (limited to 'cpukit/score/cpu/moxie/rtems/score/cpu.h')
| -rw-r--r-- | cpukit/score/cpu/moxie/rtems/score/cpu.h | 23 |
1 files changed, 0 insertions, 23 deletions
diff --git a/cpukit/score/cpu/moxie/rtems/score/cpu.h b/cpukit/score/cpu/moxie/rtems/score/cpu.h index 4b204cbb43..3422d0205e 100644 --- a/cpukit/score/cpu/moxie/rtems/score/cpu.h +++ b/cpukit/score/cpu/moxie/rtems/score/cpu.h @@ -54,29 +54,6 @@ extern "C" { #define CPU_INLINE_ENABLE_DISPATCH FALSE /* - * Should the body of the search loops in _Thread_queue_Enqueue_priority - * be unrolled one time? In unrolled each iteration of the loop examines - * two "nodes" on the chain being searched. Otherwise, only one node - * is examined per iteration. - * - * If TRUE, then the loops are unrolled. - * If FALSE, then the loops are not unrolled. - * - * The primary factor in making this decision is the cost of disabling - * and enabling interrupts (_ISR_Flash) versus the cost of rest of the - * body of the loop. On some CPUs, the flash is more expensive than - * one iteration of the loop body. In this case, it might be desirable - * to unroll the loop. It is important to note that on some CPUs, this - * code is the longest interrupt disable period in RTEMS. So it is - * necessary to strike a balance when setting this parameter. - * - * MOXIE Specific Information: - * - * XXX - */ -#define CPU_UNROLL_ENQUEUE_PRIORITY FALSE - -/* * Should this target use 16 or 32 bit object Ids? * */ |