From 620b23ece54a0bb43189bb9c0f14adf447cbafe6 Mon Sep 17 00:00:00 2001 From: Sebastian Huber Date: Thu, 24 Nov 2016 06:13:11 +0100 Subject: score: Optimize _Thread_queue_Enqueue() Move thread state for _Thread_queue_Enqueue() to the thread queue context. This reduces the parameter count of _Thread_queue_Enqueue() from five to four (ARM for example has only four function parameter registers). Since the thread state is used after several function calls inside _Thread_queue_Enqueue() this parameter was saved on the stack previously. --- cpukit/rtems/src/regiongetsegment.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) (limited to 'cpukit/rtems') diff --git a/cpukit/rtems/src/regiongetsegment.c b/cpukit/rtems/src/regiongetsegment.c index 04be73bc4b..dfd476ccc0 100644 --- a/cpukit/rtems/src/regiongetsegment.c +++ b/cpukit/rtems/src/regiongetsegment.c @@ -87,6 +87,10 @@ rtems_status_code rtems_region_get_segment( executing->Wait.return_argument = segment; /* FIXME: This is a home grown condition variable */ + _Thread_queue_Context_set_thread_state( + &queue_context, + STATES_WAITING_FOR_SEGMENT + ); _Thread_queue_Context_set_enqueue_callout( &queue_context, _Region_Enqueue_callout @@ -96,7 +100,6 @@ rtems_status_code rtems_region_get_segment( &the_region->Wait_queue.Queue, the_region->wait_operations, executing, - STATES_WAITING_FOR_SEGMENT, &queue_context ); return _Status_Get_after_wait( executing ); -- cgit v1.2.3