| commit | 22d166f058505606999922abec664d63bc05eca5 | [log] [tgz] |
|---|---|---|
| author | Keith Packard <keithp@keithp.com> | Thu May 14 20:51:13 2020 |
| committer | Keith Packard <keithp@keithp.com> | Thu May 14 20:52:24 2020 |
| tree | e27ed56a34334f6f6305b219d0e6a255a46eacaf | |
| parent | 38ae38757f412f5023129b9bccfc44e9ab7ea73d [diff] |
Add missing test-aarch64.ld file Required to be able to build tests Signed-off-by: Keith Packard <keithp@keithp.com>
Copyright © 2018,2019 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.
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.
Picolibc inherited code for a lot of architectures from newlib, but at this point only has code to build for the following targets:
Supporting architectures that already have newlib code requires:
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:
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.
This release contains an important TLS fix for ARM along with a few minor compatibility fixes
Make __aeabi_read_tp respect ARM ABI register requirements to avoid clobbering register contents during TLS variable use.
Use cpu_family instead of cpu in meson config, which is ‘more correct’ when building for a single cpu instead of multilib.
Make arm sample interrupt vector work with clang
Use __inline instead of inline in published headers to allow compiling with -ansi
Make ‘naked’ RISC-V _start function contain only asm statements as required by clang (and recommended by gcc).
Use -msave-restore in sample RISC-V cross-compile configuration. This saves text space.
This release was focused on cleaning up the copyright and license information.
Copyright information should now be present in every source file.
License information, where it could be inferred from the repository, was added to many files.
4-clause BSD licenses were changed (with permission) to 3-clause
Fix RISC-V ieeefp.h exception bits
Merge past newlib 3.2.0
Add PICOLIBC_TLS preprocessor define when the library has TLS support
This release now includes tests, and fixes bugs found by them.
ESP8266 support added, thanks to Jonathan McDowell.
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.
String/number conversion bug fixes. This includes fcvt/ecvt/gcvt shared with newlib and tinystdio printf/scanf
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.
Semihosting updates, including adding unlink, kill and getpid (which are used by some tests).
This release includes important fixes in picolibc.ld and more semihosting support.
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.
Fix picolibc.ld to not attempt to use redefined symbols for memory space definitions. These redefinitions 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.
Expose library definitions in ‘picolibc.h’, instead of ‘newlib.h’ and ‘_newlib_version.h’
Define HAVE_SEMIHOST when semihosting support is available. This lets the ‘hello-world’ example do some semihost specific things.
A minor update from 1.0, this release includes:
semihost support. This adds console I/O and exit(3) support on ARM and RISC-V hosts using the standard semihosting interfaces.
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).
Merge recent upstream newlib code. This brings picolibc up to date with current newlib sources.
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.
Remove newlib/libm/mathfp directory. This experimental code never worked correctly anyways.
This is the first release of picolibc. Major changes from newlib include:
Remove all non-BSD licensed code. None of it was used in building the embedded library, and removing it greatly simplifies the license situation.
Move thread-local values to native TLS mechanism
Add smaller stdio from avr-libc, which is enabled by default
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.
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.