-
Notifications
You must be signed in to change notification settings - Fork 2k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
19341: Picolibc updates r=benpicco a=keith-packard ### Contribution description Minor updates to picolibc support for newer versions of picolibc, including 1.8. ### Testing procedure Here's the current build result for a board I happen to have on my bench right now: ``` $ make -C examples/blinky BOARD=nucleo-f103rb FEATURES_REQUIRED=picolibc ... /home/keithp/src/RIOT/sys/picolibc_syscalls_default/syscalls.c:319:1: error: unknown type name '_READ_WRITE_RETURN_TYPE' 319 | _READ_WRITE_RETURN_TYPE read(int fd, void *dest, size_t count) | ^~~~~~~~~~~~~~~~~~~~~~~ /home/keithp/src/RIOT/sys/picolibc_syscalls_default/syscalls.c:351:1: error: unknown type name '_READ_WRITE_RETURN_TYPE' 351 | _READ_WRITE_RETURN_TYPE write(int fd, const void *src, size_t count) | ^~~~~~~~~~~~~~~~~~~~~~~ ... ``` ### Description of changes 1. Fix the read/write return values (Picolibc 1.8 uses POSIX standard types now) 2. Add new symbols to linker scripts (Picolibc needs help dealing with TLS alignment) 3. Align stack and thread local storage block during thread setup. 19345: cpu/riscv_common: convert to uword_t usage r=benpicco a=dylad ### Contribution description This PR makes use of `uword_t` type in a few places in `cpu/riscv_common`. This should not have any effect on produced binaries. ### Testing procedure CI should be enough. ### Issues/PRs references Quickly adapt from #16994. It will help for 64 bits support one day ;) Co-authored-by: Keith Packard <keithp@keithp.com> Co-authored-by: Dylan Laduranty <dylan.laduranty@mesotic.com>
- Loading branch information
Showing
8 changed files
with
44 additions
and
14 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters