Re: [PATCH] score: Unify CORE mutex seize/surrender

2016-09-27 Thread Sebastian Huber
On 27/09/16 16:59, Gedare Bloom wrote: A mostly unrelated question: why do we have two different _Semaphore_Get functions, one static in score/src/semaphore.c and the other inlined from semimpl.h? Yes, this is a bit confusing. One is part of the Classic API, the other is for the

Re: [PATCH] score: Unify CORE mutex seize/surrender

2016-09-27 Thread Gedare Bloom
OK. A mostly unrelated question: why do we have two different _Semaphore_Get functions, one static in score/src/semaphore.c and the other inlined from semimpl.h? On Tue, Sep 27, 2016 at 9:25 AM, Sebastian Huber wrote: > Use the Thread_Control::resource_count

[PATCH] score: Unify CORE mutex seize/surrender

2016-09-27 Thread Sebastian Huber
Use the Thread_Control::resource_count for the no protocol mutexes. Merge the no protocol and priority inherit CORE mutex seize/surrender operations. --- cpukit/libnetworking/rtems/rtems_glue.c | 2 + cpukit/posix/src/mutexlocksupp.c | 3 +-

Re: [PATCH] [RTEMS] Always use atomic builtins for libstdc++

2016-09-27 Thread Sebastian Huber
On 22/09/16 12:55, Jonathan Wakely wrote: [...] N.B. if you're going to require libatomic for RTEMS then you should check if the preprocessor conditions in libsupc++/exception_ptr.h and libsupc++/eh_ptr.cc are appropriate. If exception_ptr is not currently enabled for RTEMS then you could enable