Fromager Picolibc

This is the FROMAGER fork of picolibc, used when building C programs for the MicroRAM architecture.

Buildng

mkdir build
cd build
../scripts/do-fromager-configure
ninja install

This will "install" LLVM bitcode files into build/image/picolibc/x86_64-unknown-fromager/lib/.

When changing meson.build files or the build configuration, it may be necessary to rm -r build and restart from scratch, as otherwise Meson can wrongly retain settings from the old configuration. (Fortunately, picolibc builds very quickly.)

Picolibc

Copyright © 2018-2021 Keith Packard

Picolibc is library offering standard C library APIs that targets small embedded systems with limited RAM. Picolibc was formed by blending code from Newlib and AVR Libc.

Build status:

• 
• 
• 

License

Picolibc source comes from a variety of places and has a huge variety of copyright holders and license texts. While much of the code comes from Newlib, none of the GPL-related bits used to build the library are left in the repository, so all of the source code uses BSD-like licenses, a mixture of 2- and 3- clause BSD itself and a variety of other (mostly older) licenses with similar terms.

There are two files used for testing printf, test/printf-tests.c and test/testcases.c which are licensed under the GPL version 2 or later.

The file COPYING.picolibc contains all of the current copyright and license information in the Debian standard machine-readable format. It was generated using the make-copyrights and find-copyright scripts. There are currently 75 distinct licenses: 9 versions of the 2-clause BSD license, 35 versions of the 3-clause BSD license, and 31 other licenses.

Supported Architectures

Picolibc inherited code for a lot of architectures from Newlib, but at this point only has code to build for the following targets:

• ARM (32- and 64- bit)
• i386 (Linux hosted, for testing)
• RISC-V (both 32- and 64- bit)
• x86_64 (Linux hosted, for testing)
• PowerPC
• ESP8266 (xtensa-lx106-elf)

Supporting architectures that already have Newlib code requires:

1. newlib/libc/machine/architecture/meson.build to build any architecture-specific libc bits

2. newlib/libm/machine/architecture/meson.build to build any architecture-specific libm bits

3. picocrt/machine/architecture source code and build bits if you need custom startup code for the architecture. Useful in all cases, but this is necessary to run tests under qemu if your platform can do that.

4. cross-gcc-triple.txt to configure the meson cross-compilation mechanism to use the right tools

5. do-architecture-configure to make testing the cross-compilation setup easier.

6. newlib/libc/picolib support. This should include whatever startup helpers are required (like ARM interrupt vector) and TLS support (if your compiler includes this).

7. run-architecture script to run tests under QEMU. Look at the ARM and RISC-V examples to get a sense of what this needs to do and how it gets invoked from the cross-gcc-triple.txt configuration file.

Relation to newlib

Picolibc is mostly built from pieces of newlib, and retains the directory structure of that project. While there have been a lot of changes in the build system and per-thread data storage, the bulk of the source code remains unchanged.

To keep picolibc and newlib code in sync, newlib changes will be regularly incorporated. To ease integration of these changes into picolibc, some care needs to be taken while editing the code:

• Files should not be renamed.
• Fixes that also benefit users of newlib should also be sent to the newlib project
• Changes, where possible, should be made in a way compatible with newlib design. For example, instead of using 'errno' (which is valid in picolibc), use __errno_r(r), even when 'r' is not defined in the local context.

The bulk of newlib changes over the last several years have been in areas unrelated to the code used by picolibc, so keeping things in sync has not been difficult so far.

Releases

Picolibc version 1.5.1

1. Make riscv crt0 '_exit' symbol 'weak' to allow linking without this function.

Picolibc version 1.5

1. Make picolibc more compatible with C++ compilers.

2. Add GCC specs file and linker script for building C++ applications with G++ that enable exception handling by linking in call stack information.

3. A few clang build fixes, including libm exception generation

4. Nano malloc fixes, especially for 'unusual' arguments

5. Merge in newlib 4.1.0 code

6. More libm exception/errno/infinity fixes, mostly in the gamma funcs.

7. Add tests for all semihost v2.0 functions.

8. A few RISC-V assembly fixes and new libm code.

9. Build fixes to reliably replace generic code with architecture-specific implementations.

With a patch which is pending for GCC 11, we'll be able to build C++ applications that use picolibc with exceptions and iostream.

Picolibc version 1.4.7

1. Fix numerous libm exception and errno bugs. The math functions are all now verified to match the C19 and Posix standards in this area.

2. Change behavior of 'gamma' function to match glibc which returns lgamma for this function. Applications should not use this function, they should pick either lgamma or tgamma as appropriate.

3. Fix fma/fmaf on arm and RISC-V so that the machine-specific versions are used when the hardware has support. Also fix the math library to only use fma/fmaf when it is supported by the hardware.

4. Fix numerous nano-malloc bugs, especially with unusual parameters.

5. Change nano-malloc to always clear returned memory.

6. Improve nano-realloc to perform better in various ways, including merging adjacent free blocks and expanding the heap.

7. Add malloc tests, both a basic functional test and a stress test.

8. Improve build portability to Windows. Picolibc should now build using mingw.

9. Use hardware TLS register on ARM when available.

10. Support clang compiler. Thanks to Denis Feklushkin [email protected] and Joakim Nohlgård [email protected].

11. Avoid implicit float/double conversions. Check this by having clang builds use -Wdouble-promotion -Werror=double-promotion flags

12. Have portable code check for machine-specific overrides by matching filenames. This avoids building libraries with duplicate symbols and retains compatibility with newlib (which uses a different mechanism for this effect).

13. Patches to support building with CompCert, a formally verified compiler. Thanks to Sebastian Meyer [email protected].

Picolibc version 1.4.6

1. Install 'ssp' (stack smashing protection) header files. This fixes compiling with -D_FORTIFY_SOURCE.

2. Make getc/ungetc re-entrant. This feature, which is enabled by default, uses atomic instruction sequences that do not require OS support.

3. Numerous iconv fixes, including enabling testing and switching external CCS file loading to use stdio. By default, iconv provides built-in CCS data for all of the supported encodings, which takes a fairly large amount of read-only memory. Iconv is now always included in picolibc as it isn't included in applications unless explicitly referenced by them.

4. Add __getauxval stub implementation to make picolibc work with GCC version 10 compiled for aarch64-linux-gnu.

5. Change how integer- and float- only versions of printf and scanf are selected. Instead of re-defining the symbols using the C preprocessor, picolibc now re-defines the symbols at link time. This avoids having applications compiled with a mixture of modes link in multiple versions of the underlying functions, while still preserving the smallest possible integer-only implementation.

6. Document how to use picolibc on a native POSIX system for testing. Check out the os.md file for details.

7. Merge current newlib bits in. This includes better fenv support, for which tests are now included in the picolibc test suite.

Picolibc version 1.4.5

1. Fix section order in picolibc.ld to give applications correct control over the layout of .preserve, .init and .fini regions.

2. Add startup and TLS support for aarch64 and non Cortex-M 32-bit arm.

Picolibc version 1.4.4

1. Fix floating point 'g' format output in tinystdio. (e.g., for 10.0, print '10' instead of '1e+01'). There are tests which verify a range of 'g' cases like these now.

2. Merge current newlib bits. The only thing which affects picolibc is the addition of fenv support for arm.

Picolibc version 1.4.3

1. Make fix for CVE 2019-14871 - CVE 2019-14878 in original newlib stdio code not call 'abort'. Allocation failures are now reported back to the application.

2. Add 'exact' floating point print/scan code to tinystdio. Thanks to Sreepathi Pai for pointing me at the Ryu code by Ulf Adams.

3. Add regular expression functions from newlib. These were removed by accident while removing POSIX filesystem-specific code.

4. Make tinystdio versions of [efg]cvt functions. This means that the default tinystdio version of picolibc no longer calls malloc from these functions.

5. More clang-compatibility fixes. (Thanks to Denis Feklushkin)

6. Remove stdatomic.h and tgmath.h. (they should not be provide by picolibc)

Picolibc version 1.4.2

1. Clang source compatibility. Clang should now be able to compile the library. Thanks to Denis Feklushkin for figuring out how to make this work.

2. aarch64 support. This enables the existing aarch64 code and provides an example configuration file for getting it built. Thanks for Anthony Anderson for this feature.

3. Testing on github on push and pull-request. For now, this is limited to building the library due to a bug in qemu.

4. Get newlib stdio working again. You can now usefully use Newlib's stdio. This requires a working malloc and is substantially larger than tinystdio, but has more accurate floating point input. This requires POSIX functions including read, write and a few others.

5. Fix long double strtold. The working version is only available when using tinystdio; if using newlib stdio, strtold is simply not available.

6. Improve tinystdio support for C99 printf/scanf additions.

7. Check for correct prefix when sysroot-install option is selected. The value of this option depends on how gcc was configured, and (alas) meson won't let us set it at runtime, so instead we complain if the wrong value was given and display the correct value.

8. Sync up with current newlib head.

Picolibc version 1.4.1

This release contains an important TLS fix for ARM along with a few minor compatibility fixes

1. Make __aeabi_read_tp respect ARM ABI register requirements to avoid clobbering register contents during TLS variable use.

2. Use cpu_family instead of cpu in meson config, which is 'more correct' when building for a single cpu instead of multilib.

3. Make arm sample interrupt vector work with clang

4. Use __inline instead of inline in published headers to allow compiling with -ansi

5. Make 'naked' RISC-V _start function contain only asm statements as required by clang (and recommended by gcc).

6. Use -msave-restore in sample RISC-V cross-compile configuration. This saves text space.

Picolibc version 1.4

This release was focused on cleaning up the copyright and license information.

1. Copyright information should now be present in every source file.

2. License information, where it could be inferred from the repository, was added to many files.

3. 4-clause BSD licenses were changed (with permission) to 3-clause

4. Fix RISC-V ieeefp.h exception bits

5. Merge past newlib 3.2.0

6. Add PICOLIBC_TLS preprocessor define when the library has TLS support

Picolibc version 1.3

This release now includes tests, and fixes bugs found by them.

1. ESP8266 support added, thanks to Jonathan McDowell.

2. Numerous test cases from newlib have been fixed, and precision requirements adjusted so that the library now passes its own test suite on x86, RISC-V and ARM.

3. String/number conversion bug fixes. This includes fcvt/ecvt/gcvt shared with newlib and tinystdio printf/scanf

4. A few RISC-V ABI fixes, including setting the TLS base correctly, compiling with -mcmodel=medany, and enabling the FPU for libraries built to use it.

5. Semihosting updates, including adding unlink, kill and getpid (which are used by some tests).

Picolibc version 1.2

This release includes important fixes in picolibc.ld and more semihosting support.

1. File I/O and clock support for semihosting. This enables fopen/fdopen support in tinystdio along with an API to fetch a real time clock value.

2. Fix picolibc.ld to not attempt to use redefined symbols for memory space definitions. These re-definitions would fail and the default values be used for system memory definitions. Instead, just use the ? : operators each place the values are needed. Linker scripts continue to mystify.

3. Expose library definitions in 'picolibc.h', instead of 'newlib.h' and '_newlib_version.h'

4. Define HAVE_SEMIHOST when semihosting support is available. This lets the 'hello-world' example do some semihost specific things.

Picolibc version 1.1

A minor update from 1.0, this release includes:

1. semihost support. This adds console I/O and exit(3) support on ARM and RISC-V hosts using the standard semihosting interfaces.

2. Posix I/O support in tinystdio. When -Dposix-io=true is included in the meson command line (which is the default), tinystdio adds support for fopen and fdopen by using malloc, open, close, read, write and lseek. If -Dposix-console=true is also passed to meson, then picolibc will direct stdin/stdout/stderr to the posix standard file descriptors (0, 1, 2).

3. Merge recent upstream newlib code. This brings picolibc up to date with current newlib sources.

4. Hello world example. This uses a simple Makefile to demonstrate how to us picolibc when installed for ARM and RISC-V embedded processors. The resulting executables can be run under qemu.

5. Remove newlib/libm/mathfp directory. This experimental code never worked correctly anyways.

Picolibc version 1.0

This is the first release of picolibc. Major changes from newlib include:

1. Remove all non-BSD licensed code. None of it was used in building the embedded library, and removing it greatly simplifies the license situation.

2. Move thread-local values to native TLS mechanism

3. Add smaller stdio from avr-libc, which is enabled by default

4. Switch build system to meson. This has two notable benefits; the first is that building the library is much faster, the second is that it isolates build system changes from newlib making merging of newlib changes much easier.

5. Add simple startup code. This can be used in environments that don't have complicated requirements, allowing small applications to avoid needing to figure this out.

Documentation

• Building Picolibc
• Operating System Support
• Printf and Scanf in Picolibc
• Using Picolibc
• Picolibc initialization
• Thread Local Storage
• Linking with Picolibc.ld
• Hello World
• Picolibc as embedded source
• Releasing Picolibc
• Copyright and license information