From ef1be69b652176addf58eb097887dc75c8522dc1 Mon Sep 17 00:00:00 2001 From: Joel Sherrill Date: Wed, 11 Feb 2009 21:44:59 +0000 Subject: 2009-02-11 Joel Sherrill * rtems/new-exceptions/cpu.h, rtems/score/cpu.h: Eliminate _CPU_Thread_dispatch_pointer and passing address of _Thread_Dispatch to _CPU_Initialize. Clean up comments. --- cpukit/score/cpu/powerpc/rtems/new-exceptions/cpu.h | 12 ------------ 1 file changed, 12 deletions(-) (limited to 'cpukit/score/cpu/powerpc/rtems/new-exceptions') diff --git a/cpukit/score/cpu/powerpc/rtems/new-exceptions/cpu.h b/cpukit/score/cpu/powerpc/rtems/new-exceptions/cpu.h index 649019fbd9..d620c5eb5d 100644 --- a/cpukit/score/cpu/powerpc/rtems/new-exceptions/cpu.h +++ b/cpukit/score/cpu/powerpc/rtems/new-exceptions/cpu.h @@ -189,18 +189,6 @@ SCORE_EXTERN void *_CPU_Interrupt_stack_high; #define CPU_MODES_INTERRUPT_LEVEL 0x00000001 /* interrupt level in mode */ #define CPU_MODES_INTERRUPT_MASK 0x00000001 /* interrupt level in mode */ -/* - * 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). - */ - -/* EXTERN void (*_CPU_Thread_dispatch_pointer)(); */ - /* * Nothing prevents the porter from declaring more CPU specific variables. */ -- cgit v1.2.3