From acc6d9bf37361c49039d8a3a33ad6cb05b5c38b9 Mon Sep 17 00:00:00 2001 From: Sebastian Huber Date: Thu, 10 Nov 2016 07:12:55 +0100 Subject: score: Remove obsolete defines The thread dispatch inline option is no longer used. --- cpukit/score/cpu/epiphany/rtems/score/cpu.h | 20 -------------------- 1 file changed, 20 deletions(-) (limited to 'cpukit/score/cpu/epiphany/rtems/score/cpu.h') diff --git a/cpukit/score/cpu/epiphany/rtems/score/cpu.h b/cpukit/score/cpu/epiphany/rtems/score/cpu.h index 2954628a58..4c9d3fceea 100644 --- a/cpukit/score/cpu/epiphany/rtems/score/cpu.h +++ b/cpukit/score/cpu/epiphany/rtems/score/cpu.h @@ -49,26 +49,6 @@ extern "C" { /* conditional compilation parameters */ -/* - * Should the calls to _Thread_Enable_dispatch be inlined? - * - * If TRUE, then they are inlined. - * If FALSE, then a subroutine call is made. - * - * Basically this is an example of the classic trade-off of size - * versus speed. Inlining the call (TRUE) typically increases the - * size of RTEMS while speeding up the enabling of dispatching. - * [NOTE: In general, the _Thread_Dispatch_disable_level will - * only be 0 or 1 unless you are in an interrupt handler and that - * interrupt handler invokes the executive.] When not inlined - * something calls _Thread_Enable_dispatch which in turns calls - * _Thread_Dispatch. If the enable dispatch is inlined, then - * one subroutine call is avoided entirely.] - * - */ - -#define CPU_INLINE_ENABLE_DISPATCH FALSE - /* * Does RTEMS manage a dedicated interrupt stack in software? * -- cgit v1.2.3