summaryrefslogtreecommitdiffstats
path: root/posix-users/status_of_implementation.rst
diff options
context:
space:
mode:
authorChris Johns <chrisj@rtems.org>2016-11-03 16:58:08 +1100
committerChris Johns <chrisj@rtems.org>2016-11-03 16:58:08 +1100
commit72a62ad88f82fe1ffee50024db4dd0f3fa5806f7 (patch)
tree6b0e527e67141f8126ba56b8a3c1eb90aeed5849 /posix-users/status_of_implementation.rst
parent6207c37d9c8a3d75e67c10671fe2c309c805bbed (diff)
downloadrtems-docs-72a62ad88f82fe1ffee50024db4dd0f3fa5806f7.tar.bz2
Rename all manuals with an _ to have a -. It helps released naming of files.
Diffstat (limited to 'posix-users/status_of_implementation.rst')
-rw-r--r--posix-users/status_of_implementation.rst46
1 files changed, 46 insertions, 0 deletions
diff --git a/posix-users/status_of_implementation.rst b/posix-users/status_of_implementation.rst
new file mode 100644
index 0000000..cc234fc
--- /dev/null
+++ b/posix-users/status_of_implementation.rst
@@ -0,0 +1,46 @@
+.. comment SPDX-License-Identifier: CC-BY-SA-4.0
+
+Status of Implementation
+########################
+
+This chapter provides an overview of the status of the implementation
+of the POSIX API for RTEMS. The *POSIX 1003.1b Compliance Guide*
+provides more detailed information regarding the implementation of
+each of the numerous functions, constants, and macros specified by
+the POSIX 1003.1b standard.
+
+RTEMS supports many of the process and user/group oriented services
+in a "single user/single process" manner. This means that although
+these services may be of limited usefulness or functionality, they
+are provided and do work in a coherent manner. This is significant
+when porting existing code from UNIX to RTEMS.
+
+- Implementation
+
+ - The current implementation of ``dup()`` is insufficient.
+ - FIFOs ``mkfifo()`` are not currently implemented.
+ - Asynchronous IO is not implemented.
+ - The ``flockfile()`` family is not implemented
+ - getc/putc unlocked family is not implemented
+ - Shared Memory is not implemented
+ - Mapped Memory is not implemented
+ - NOTES:
+
+ - For Shared Memory and Mapped Memory services, it is unclear what
+ level of support is appropriate and possible for RTEMS.
+
+- Functional Testing
+
+ - Tests for unimplemented services
+
+- Performance Testing
+
+ - There are no POSIX Performance Tests.
+
+- Documentation
+
+ - Many of the service description pages are not complete in this
+ manual. These need to be completed and information added to the
+ background and operations sections.
+
+ - Example programs (not just tests) would be very nice.