From c03e2bc8c7b6c2133db6a661d785409d4756149a Mon Sep 17 00:00:00 2001 From: Joel Sherrill Date: Wed, 11 Feb 2009 21:45:05 +0000 Subject: 2009-02-11 Joel Sherrill * cpu.c, rtems/score/cpu.h: Eliminate _CPU_Thread_dispatch_pointer and passing address of _Thread_Dispatch to _CPU_Initialize. Clean up comments. --- cpukit/score/cpu/c4x/rtems/score/cpu.h | 22 +--------------------- 1 file changed, 1 insertion(+), 21 deletions(-) (limited to 'cpukit/score/cpu/c4x/rtems/score/cpu.h') diff --git a/cpukit/score/cpu/c4x/rtems/score/cpu.h b/cpukit/score/cpu/c4x/rtems/score/cpu.h index d6be49c19a..8c15ec6f52 100644 --- a/cpukit/score/cpu/c4x/rtems/score/cpu.h +++ b/cpukit/score/cpu/c4x/rtems/score/cpu.h @@ -580,24 +580,6 @@ SCORE_EXTERN Context_Control_fp _CPU_Null_fp_context; SCORE_EXTERN void *_CPU_Interrupt_stack_low; SCORE_EXTERN void *_CPU_Interrupt_stack_high; -/* - * With some compilation systems, it is difficult if not impossible to - * call a high-level language routine from assembly language. This - * is especially true of commercial Ada compilers and name mangling - * C++ ones. This variable can be optionally defined by the CPU porter - * and contains the address of the routine _Thread_Dispatch. This - * can make it easier to invoke that routine at the end of the interrupt - * sequence (if a dispatch is necessary). - * - * C4x Specific Information: - * - * This port should not require this. - */ - -#if 0 -SCORE_EXTERN void (*_CPU_Thread_dispatch_pointer)(); -#endif - /* * Nothing prevents the porter from declaring more CPU specific variables. * @@ -1078,9 +1060,7 @@ void _CPU_Context_Initialize( * XXXanswer */ -void _CPU_Initialize( - void (*thread_dispatch) -); +void _CPU_Initialize(void); /* * _CPU_ISR_install_raw_handler -- cgit v1.2.3