POSIX Compliance

Student(s): Vaibhav Gupta.

Mentors: Joel Sherrill, Aditya Upadhyay, Hesham .

Ticket: ​POSIX Compliance

Development Blog: ​My GSoC 2019 Journey

Introduction to Project

Project Description

(Content Derived from my Proposal) This Project deals with the implementation of a subset of functions that is defined in FACE (8) Technical Standard 3.0 and POSIX (6) IEEE Standard 1003.1™ . Due to physical resource constraints some real time systems like small embedded system needs limited set of operating system functionality. For these type of system it is necessary that the standards allow implementation to support only a particular subset of POSIX functions. For instance, there is an approved change request against FACE 3.0 to make support for multiple processes optional. Any method listed in the FACE Technical Standard Edition 3.0, in Appendix A.1 as POSIX_MULTI_PROCESS is now optional. This is logical for embedded systems like RTEMS which follows Single Process Multi Threading Concept.

Project Goal

The goal is to add missing functions and libraries to newlib, which in turn will make RTEMS complaint to latest POSIX and FACE standards.

Project Setup

• Project Sandboxing on my System: ​https://github.com/VARoDeK/MyNotes/blob/master/RTEMS/project_sandboxing.md

• Steps I followed to setup RTEMS on host OS (my system): ​https://github.com/VARoDeK/MyNotes/tree/master/RTEMS/InstallOnHost

References

• (1) My Notes: ​https://github.com/VARoDeK/MyNotes/tree/master/RTEMS

• (5) ​https://www.sourceware.org/newlib/

• (6) ​https://en.wikipedia.org/wiki/POSIX

• (7) ​https://en.wikipedia.org/wiki/C_standard_library

• (8) ​https://en.wikipedia.org/wiki/Future_Airborne_Capability_Environment

• (9) ​https://en.wikipedia.org/wiki/Institute_of_Electrical_and_Electronics_Engineers