c11c1dc8fd
Modify reason: When build Nuttx SIM, in x86_64 system: Compile with gcc option '-m64' (default): sizeof(double_t) = 8 sizeof(double) = 8 Compile with gcc option '-mx32': sizeof(double_t) = 8 sizeof(double) = 8 Compile with gcc option '-m32': sizeof(double_t) = 12 // long double sizeof(double) = 8 When use '-m32', and print sth. like this: printf("%f\n", (double)3.0); SIM will print out: nan This is because sizeof(double_t) is not equal with double. Resolve: replace all double_t to double in libs/libc/stdio. As a user of '-m32', you should know double_t is one type long double, and len is 12. And you use use '%lf' to print. like: printf("%lf\n", (double_t)3.0); Currently we don't support '%lf'. Change-Id: I9b9d11853140d5296dd80416c8ed6a260a9d2d9c Signed-off-by: ligd <liguiding1@xiaomi.com> |
||
---|---|---|
.. | ||
libc | ||
libdsp | ||
libnx | ||
libxx | ||
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.