From 029877282edb8aa7a2095702742ce95c8246729e Mon Sep 17 00:00:00 2001 From: Sebastian Huber Date: Wed, 29 Jun 2016 15:33:26 +0200 Subject: score: Avoid atomic fences for thread wait flags The use of atomic fences is brittle and may break due to changes in different areas which is hard to manage. --- cpukit/rtems/src/eventsurrender.c | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) (limited to 'cpukit/rtems/src/eventsurrender.c') diff --git a/cpukit/rtems/src/eventsurrender.c b/cpukit/rtems/src/eventsurrender.c index 576670b0b7..a9bef5916c 100644 --- a/cpukit/rtems/src/eventsurrender.c +++ b/cpukit/rtems/src/eventsurrender.c @@ -91,11 +91,8 @@ rtems_status_code _Event_Surrender( _Event_Satisfy( the_thread, event, pending_events, seized_events ); - /* See _Event_Seize() */ - _Atomic_Fence( ATOMIC_ORDER_RELEASE ); - ready_again = wait_class | THREAD_WAIT_STATE_READY_AGAIN; - success = _Thread_Wait_flags_try_change_critical( + success = _Thread_Wait_flags_try_change_release( the_thread, wait_class | THREAD_WAIT_STATE_INTEND_TO_BLOCK, ready_again -- cgit v1.2.3