Skip to content

picolibc: Update to version proposed for Zephyr main #977

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged

Conversation

keith-packard
Copy link
Contributor

Fast forward to upstream version containing a fix for a C++ incompatibility where isinf and isnan were incorrectly declared as C functions.

This version also contains another useful change to disable the picolibc malloc implementation when built as a Zephyr module. This should improve error messages with Zephyr projects which use malloc but fail to define CONFIG_COMMON_LIBC_MALLOC.

There are also minor cleanups in a few math functions in how FE_INEXACT exceptions are generated and AArch32 A-profile aeabi memcpy functions.

Zephyr PR for this same version:

https://github.com/zephyrproject-rtos/zephyr/pull/93529

Fast forward to upstream version containing a fix for a C++
incompatibility where isinf and isnan were incorrectly declared as C
functions.

This version also contains another useful change to disable the
picolibc malloc implementation when built as a Zephyr module. This
should improve error messages with Zephyr projects which use malloc
but fail to define CONFIG_COMMON_LIBC_MALLOC.

There are also minor cleanups in a few math functions in how
FE_INEXACT exceptions are generated and AArch32 A-profile aeabi memcpy
functions.

Zephyr PR for this same version:

	zephyrproject-rtos/zephyr#93529

Signed-off-by: Keith Packard <keithp@keithp.com>
@stephanosio stephanosio merged commit a693b76 into zephyrproject-rtos:v0.17-branch Jul 24, 2025
40 checks passed
@stephanosio
Copy link
Member

@keith-packard I just realised that this PR was opened against v0.17-branch.

Is this intentional? The picolibc ref at v0.17-branch should stay at Zephyr 4.2 level to ensure that 0.17.3 can be used with Zephyr 4.2.

For the latest picolibc changes going into Zephyr main, they should go into sdk-ng main, not v0.17-branch -- Zephyr main will be moving to SDK 1.0.0 once released.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants