incubator-nuttx

History

Gregory Nutt 9aaeaefa41 TLS: Correct handling of returned error values. I not two problems in handling of the return error values in PR #3858: 1. In KERNEL mode, the error return value of _SEM_WAIT() will be a negated errno value; in all other modes, it will be -1 (ERROR) with the errno variable set. This must be handled in the test of the returned value: Don't compare with -1; rather check if < 0 2. Also, conversion of the returned value to a negated errno value must be handled differently. This is handled by replacing -get_errno() with the macro _ERRVAL(ret) This effects only error handling (it fixes it) and no other impacts are expected.		2021-06-07 22:32:42 -03:00
..
libc	TLS: Correct handling of returned error values.	2021-06-07 22:32:42 -03:00
libdsp	libdsp/fixed16: add openloop handler	2021-04-01 14:54:33 -03:00
libnx	Documentation, comments: Minor improvements and typos fixed	2021-05-09 19:12:13 -07:00
libxx	libs: libxx: update licenses to Apache	2021-05-27 08:07:25 +09:00
README.txt	…

README.txt

README
======

This directory holds NuttX libraries.  Libraries in NuttX are very special
creatures.  They have these properties:

1. They can be shared by both application logic and logic within the OS when
   using the FLAT build.

2. But in PROTECTED and KERNEL modes, they must be built differently:  The
   copies used by applications and the OS cannot be the same.  Rather,
   separate versions of libraries must be built for the kernel and for
   applications.

3. When used by the OS, some special care must be taken to assure that the
   OS logic does not disrupt the user's errno value and that the OS does
   not create inappropriate cancellation points.

   For example, sem_wait() is both a cancellation point and modifies the
   errno value.  So within the FLAT build and without kernel version for
   the PROTECTED and KERNEL builds, the special internal OS interface
   nxsem_wait() must be used.  Within libraries, the macro _SEM_WAIT()
   (as defined in include/nuttx/semaphore.h) is used instead.  The
   definition of this macro accounts for the different usage environments.

NOTE:  The libraries under libs/ build differently from other NuttX
components:  There are no build-related files in the libs/ directory; it
is simply a container for other well-known, individual library directories.
The upper level Makefile logic is aware of the libraries within the libs/
container.

The only real function of the libs/ directory is to prevent the top-level
directory from becoming cluttered with individual libraries.