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 self-contained
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 for the no protocol mutexes.
> Merge t
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 +-
cpukit/posix/src/mutexunlock.
On 23/09/16 15:45, Gedare Bloom wrote:
Rather than using refcnts, is there a costlier method (e.g. iterating
some structures) to discover a thread is holding a mutex at this point
of thread destruction that makes sense to use instead?
For the Classic and POSIX object based mutexes this would be
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