From b04b76c6a0c87ffc9670d356e793108411ce355a Mon Sep 17 00:00:00 2001 From: Sebastian Huber Date: Tue, 7 Jun 2016 21:36:48 +0200 Subject: score: Simplify priority bit map implementation The priority bit map can deal with a maximum of 256 priority values ranging from 0 to 255. Consistently use an unsigned int for computation, due to the usual integer promotion rules. Make Priority_bit_map_Word definition architecture-independent and define it to uint16_t. This was already the case for all architectures except PowerPC. Adjust the PowerPC bitmap support accordingly. --- cpukit/score/cpu/sparc/rtems/score/types.h | 9 --------- 1 file changed, 9 deletions(-) (limited to 'cpukit/score/cpu/sparc/rtems/score/types.h') diff --git a/cpukit/score/cpu/sparc/rtems/score/types.h b/cpukit/score/cpu/sparc/rtems/score/types.h index 4186012589..6419c9f15f 100644 --- a/cpukit/score/cpu/sparc/rtems/score/types.h +++ b/cpukit/score/cpu/sparc/rtems/score/types.h @@ -30,15 +30,6 @@ extern "C" { /** Type that can store a 32-bit integer or a pointer. */ typedef uintptr_t CPU_Uint32ptr; -/** - * @brief Priority bit map type. - * - * On the SPARC, there is no bitscan instruction and no penalty associated - * for using 16-bit variables. With no overriding architectural factors, - * just using a uint16_t. - */ -typedef uint16_t Priority_bit_map_Word; - /** * @brief SPARC ISR handler return type. * -- cgit v1.2.3