Mirrors_Framework/rtems
1
0
Fork 0
mirror of https://gitlab.rtems.org/rtems/rtos/rtems.git synced 2026-09-21 22:44:02 +08:00
Code Issues Packages Projects Releases Wiki Activity

score: Remove obsolete defines

Browse Source 
The thread dispatch inline option is no longer used.
This commit is contained in:
Sebastian Huber
2016-11-18 07:30:31 +01:00
parent 0e658d456c
commit acc6d9bf37
18 changed files with 0 additions and 281 deletions
Download Patch File Download Diff File Expand all files Collapse all files
cpukit/score/cpu/arm/rtems/score/cpu.h
-7
View File
@@ -97,13 +97,6 @@
*/
/**@{**/
/* If someone uses THUMB we assume she wants minimal code size */
#ifdef __thumb__
#define CPU_INLINE_ENABLE_DISPATCH FALSE
#else
#define CPU_INLINE_ENABLE_DISPATCH TRUE
#endif
#if defined(__ARMEL__)
#define CPU_BIG_ENDIAN FALSE
#define CPU_LITTLE_ENDIAN TRUE
cpukit/score/cpu/bfin/rtems/score/cpu.h
-23
View File
@@ -30,29 +30,6 @@ extern "C" {
/* conditional compilation parameters */
/**
* Should the calls to @ref _Thread_Enable_dispatch be inlined?
*
* If TRUE, then they are inlined.
* If FALSE, then a subroutine call is made.
*
* This conditional 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 @ref _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 @ref _Thread_Enable_dispatch which in turns calls
* @ref _Thread_Dispatch. If the enable dispatch is inlined, then
* one subroutine call is avoided entirely.
*
* Port Specific Information:
*
* XXX document implementation including references if appropriate
*/
#define CPU_INLINE_ENABLE_DISPATCH FALSE
/**
* Does RTEMS manage a dedicated interrupt stack in software?
*
cpukit/score/cpu/epiphany/rtems/score/cpu.h
-20
View File
@@ -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?
*
cpukit/score/cpu/i386/rtems/score/cpu.h
-2
View File
@@ -32,8 +32,6 @@ extern "C" {
/* conditional compilation parameters */
#define CPU_INLINE_ENABLE_DISPATCH TRUE
/*
* Does the CPU follow the simple vectored interrupt model?
*
cpukit/score/cpu/lm32/rtems/score/cpu.h
-23
View File
@@ -28,29 +28,6 @@ extern "C" {
/* conditional compilation parameters */
/**
* Should the calls to @ref _Thread_Enable_dispatch be inlined?
*
* If TRUE, then they are inlined.
* If FALSE, then a subroutine call is made.
*
* This conditional 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 @ref _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 @ref _Thread_Enable_dispatch which in turns calls
* @ref _Thread_Dispatch. If the enable dispatch is inlined, then
* one subroutine call is avoided entirely.
*
* Port Specific Information:
*
* XXX document implementation including references if appropriate
*/
#define CPU_INLINE_ENABLE_DISPATCH FALSE
/**
* Does RTEMS manage a dedicated interrupt stack in software?
*
cpukit/score/cpu/m32c/rtems/score/cpu.h
-23
View File
@@ -44,29 +44,6 @@ extern "C" {
#define RTEMS_USE_16_BIT_OBJECT
/**
* Should the calls to @ref _Thread_Enable_dispatch be inlined?
*
* If TRUE, then they are inlined.
* If FALSE, then a subroutine call is made.
*
* This conditional 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 @ref _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 @ref _Thread_Enable_dispatch which in turns calls
* @ref _Thread_Dispatch. If the enable dispatch is inlined, then
* one subroutine call is avoided entirely.
*
* Port Specific Information:
*
* XXX document implementation including references if appropriate
*/
#define CPU_INLINE_ENABLE_DISPATCH FALSE
/**
* Does RTEMS manage a dedicated interrupt stack in software?
*
cpukit/score/cpu/m68k/rtems/score/cpu.h
-2
View File
@@ -28,8 +28,6 @@ extern "C" {
/* conditional compilation parameters */
#define CPU_INLINE_ENABLE_DISPATCH TRUE
/*
* Does the CPU follow the simple vectored interrupt model?
*
cpukit/score/cpu/mips/rtems/score/cpu.h
-19
View File
@@ -61,25 +61,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?
*
cpukit/score/cpu/moxie/rtems/score/cpu.h
-22
View File
@@ -31,28 +31,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.]
*
* MOXIE Specific Information:
*
* XXX
*/
#define CPU_INLINE_ENABLE_DISPATCH FALSE
/*
* Should this target use 16 or 32 bit object Ids?
*
cpukit/score/cpu/nios2/rtems/score/cpu.h
-5
View File
@@ -27,11 +27,6 @@ extern "C" {
#include <rtems/score/types.h>
#include <rtems/score/nios2.h>
/*
* TODO: Run the timing tests and figure out what is better.
*/
#define CPU_INLINE_ENABLE_DISPATCH FALSE
#define CPU_HAS_SOFTWARE_INTERRUPT_STACK TRUE
#define CPU_SIMPLE_VECTORED_INTERRUPTS TRUE
cpukit/score/cpu/no_cpu/rtems/score/cpu.h
-23
View File
@@ -45,29 +45,6 @@ extern "C" {
/* conditional compilation parameters */
/**
* Should the calls to @ref _Thread_Enable_dispatch be inlined?
*
* If TRUE, then they are inlined.
* If FALSE, then a subroutine call is made.
*
* This conditional 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 @ref _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 @ref _Thread_Enable_dispatch which in turns calls
* @ref _Thread_Dispatch. If the enable dispatch is inlined, then
* one subroutine call is avoided entirely.
*
* Port Specific Information:
*
* XXX document implementation including references if appropriate
*/
#define CPU_INLINE_ENABLE_DISPATCH FALSE
/**
* Does RTEMS manage a dedicated interrupt stack in software?
*
cpukit/score/cpu/or1k/rtems/score/cpu.h
-20
View File
@@ -39,26 +39,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?
*
cpukit/score/cpu/powerpc/rtems/score/cpu.h
-19
View File
@@ -49,25 +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 this port provide a CPU dependent IDLE task implementation?
*
cpukit/score/cpu/sh/rtems/score/cpu.h
-19
View File
@@ -36,25 +36,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 the CPU follow the simple vectored interrupt model?
*
cpukit/score/cpu/sparc/rtems/score/cpu.h
-10
View File
@@ -53,16 +53,6 @@ extern "C" {
#define SPARC_USE_SAFE_FP_SUPPORT
#endif
/**
* Should the calls to _Thread_Enable_dispatch be inlined?
*
* - If TRUE, then they are inlined.
* - If FALSE, then a subroutine call is made.
*
* On this port, it is faster to inline _Thread_Enable_dispatch.
*/
#define CPU_INLINE_ENABLE_DISPATCH TRUE
/**
* Does the executive manage a dedicated interrupt stack in software?
*
cpukit/score/cpu/sparc64/rtems/score/cpu.h
-9
View File
@@ -33,15 +33,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.
*/
#define CPU_INLINE_ENABLE_DISPATCH TRUE
/*
* Does the executive manage a dedicated interrupt stack in software?
*
cpukit/score/cpu/v850/rtems/score/cpu.h
-24
View File
@@ -28,30 +28,6 @@ extern "C" {
/* conditional compilation parameters */
/**
* Should the calls to @ref _Thread_Enable_dispatch be inlined?
*
* If TRUE, then they are inlined.
* If FALSE, then a subroutine call is made.
*
* This conditional 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 @ref _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 @ref _Thread_Enable_dispatch which in turns calls
* @ref _Thread_Dispatch. If the enable dispatch is inlined, then
* one subroutine call is avoided entirely.
*
* Port Specific Information:
*
* The v850 is a RISC CPU which typically has enough memory to justify
* the inlining of this method.
*/
#define CPU_INLINE_ENABLE_DISPATCH TRUE
/**
* Does RTEMS manage a dedicated interrupt stack in software?
*
cpukit/score/include/rtems/score/threaddispatch.h
-11
View File
@@ -22,17 +22,6 @@
extern "C" {
#endif /* __cplusplus */
#if defined(RTEMS_HEAVY_STACK_DEBUG) || \
defined(RTEMS_HEAVY_MALLOC_DEBUG)
#define __THREAD_DO_NOT_INLINE_DISABLE_DISPATCH__
#endif
#if defined(RTEMS_SMP) || \
(CPU_INLINE_ENABLE_DISPATCH == FALSE) || \
(__RTEMS_DO_NOT_INLINE_THREAD_ENABLE_DISPATCH__ == 1)
#define __THREAD_DO_NOT_INLINE_ENABLE_DISPATCH__
#endif
/**
* @addtogroup ScoreThread
*