URL
https://opencores.org/ocsvn/or1k/or1k/trunk
Details |
Compare with Previous |
View Log
Line No. |
Rev |
Author |
Line |
1 |
1026 |
ivang |
@c
|
2 |
|
|
@c COPYRIGHT (c) 1988-2002.
|
3 |
|
|
@c On-Line Applications Research Corporation (OAR).
|
4 |
|
|
@c All rights reserved.
|
5 |
|
|
@c
|
6 |
|
|
@c preface.texi,v 1.6 2002/01/17 21:47:45 joel Exp
|
7 |
|
|
@c
|
8 |
|
|
|
9 |
|
|
@ifinfo
|
10 |
|
|
@node Preface, General, Top, Top
|
11 |
|
|
@end ifinfo
|
12 |
|
|
|
13 |
|
|
@unnumbered Preface
|
14 |
|
|
|
15 |
|
|
This document lists the functions, constant, macros, feature flags,
|
16 |
|
|
and types defined in the POSIX 1003.1 standard. Each section in
|
17 |
|
|
this document corresponds to a section in the 1003.1 standard
|
18 |
|
|
and the implementation status of the items required by the standard
|
19 |
|
|
are listed.
|
20 |
|
|
|
21 |
|
|
RTEMS supports a number of POSIX process, user, and group oriented
|
22 |
|
|
routines in what is referred to as a "SUSP" (Single-User, Single
|
23 |
|
|
Process) manner. RTEMS supports a single process, multithreaded
|
24 |
|
|
POSIX 1003.1b environment. In a pure world, there would be
|
25 |
|
|
no reason to even include routines like @code{getpid()} when there
|
26 |
|
|
can only be one process. But providing routines like @code{getpid()}
|
27 |
|
|
and making them work in a sensible fashion for an embedded environment
|
28 |
|
|
while not returning ENOSYS (for not implemented) makes it significantly
|
29 |
|
|
easier to port code from a UNIX environment without modifying it.
|
© copyright 1999-2024
OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.