diff options
author | Joel Sherrill <joel.sherrill@OARcorp.com> | 2009-06-24 06:38:52 +0000 |
---|---|---|
committer | Joel Sherrill <joel.sherrill@OARcorp.com> | 2009-06-24 06:38:52 +0000 |
commit | 2212a2adf9f760bd01ebaed18664569a302adc9b (patch) | |
tree | 22e0bc1c0f38ded2fc2093369d7b90dc9fafa6ff /cpukit/posix/inline | |
parent | 2009-06-24 Joel Sherrill <joel.sherrill@oarcorp.com> (diff) | |
download | rtems-2212a2adf9f760bd01ebaed18664569a302adc9b.tar.bz2 |
2009-06-24 Joel Sherrill <joel.sherrill@oarcorp.com>
* posix/Makefile.am, posix/include/rtems/posix/priority.h,
posix/include/rtems/posix/pthread.h,
posix/inline/rtems/posix/priority.inl, posix/src/killinfo.c,
posix/src/pthread.c, posix/src/pthreadcreate.c,
posix/src/pthreadsetschedparam.c: Various modifications to improve
binary code coverage analysis. Some of these are to mark code as
debug only. Some are to break conditional expressions into multiple
lines. Some are to move inline methods that are not time critical
into subroutines to make them easier to test. Inlining them multiple
times means that their logic paths are spread across multiple
methods. This explodes the test cases required.
* posix/src/psxpriorityisvalid.c, posix/src/psxtransschedparam.c: New files.
Diffstat (limited to 'cpukit/posix/inline')
-rw-r--r-- | cpukit/posix/inline/rtems/posix/priority.inl | 19 |
1 files changed, 1 insertions, 18 deletions
diff --git a/cpukit/posix/inline/rtems/posix/priority.inl b/cpukit/posix/inline/rtems/posix/priority.inl index 74287bd9f3..9a9f538a61 100644 --- a/cpukit/posix/inline/rtems/posix/priority.inl +++ b/cpukit/posix/inline/rtems/posix/priority.inl @@ -3,7 +3,7 @@ */ /* - * COPYRIGHT (c) 1989-2007. + * COPYRIGHT (c) 1989-2009. * On-Line Applications Research Corporation (OAR). * * The license and distribution terms for this file may be @@ -20,23 +20,6 @@ #ifndef _RTEMS_POSIX_PRIORITY_INL #define _RTEMS_POSIX_PRIORITY_INL -/* - * 1003.1b-1993,2.2.2.80 definition of priority, p. 19 - * - * "Numerically higher values represent higher priorities." - * - * Thus, RTEMS Core has priorities run in the opposite sense of the POSIX API. - */ - -RTEMS_INLINE_ROUTINE bool _POSIX_Priority_Is_valid( - int priority -) -{ - return ((priority >= POSIX_SCHEDULER_MINIMUM_PRIORITY) && - (priority <= POSIX_SCHEDULER_MAXIMUM_PRIORITY)); - -} - RTEMS_INLINE_ROUTINE Priority_Control _POSIX_Priority_To_core( int priority ) |