From 8ac3549db324367d331b779676212c0a0e3cea7b Mon Sep 17 00:00:00 2001 From: Sebastian Huber Date: Wed, 4 Mar 2015 16:13:49 +0100 Subject: score: Delete unused CPU_UNROLL_ENQUEUE_PRIORITY --- cpukit/score/cpu/sparc64/rtems/score/cpu.h | 17 ----------------- 1 file changed, 17 deletions(-) (limited to 'cpukit/score/cpu/sparc64/rtems/score') diff --git a/cpukit/score/cpu/sparc64/rtems/score/cpu.h b/cpukit/score/cpu/sparc64/rtems/score/cpu.h index ff58fc97d7..a222c0b10a 100644 --- a/cpukit/score/cpu/sparc64/rtems/score/cpu.h +++ b/cpukit/score/cpu/sparc64/rtems/score/cpu.h @@ -42,23 +42,6 @@ extern "C" { #define CPU_INLINE_ENABLE_DISPATCH TRUE -/* - * 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. - * - * This parameter could go either way on the SPARC. The interrupt flash - * code is relatively lengthy given the requirements for nops following - * writes to the psr. But if the clock speed were high enough, this would - * not represent a great deal of time. - */ - -#define CPU_UNROLL_ENQUEUE_PRIORITY TRUE - /* * Does the executive manage a dedicated interrupt stack in software? * -- cgit v1.2.3