Skip to content

picolibc: Disable exceptions for picolibc libstdc++ #33

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

Draft
wants to merge 1 commit into
base: zephyr-crosstool-ng-1.25.0
Choose a base branch
from

Conversation

adigie
Copy link

@adigie adigie commented Feb 27, 2025

Add CT_LIBC_PICOLIBC_GCC_LIBSTDCXX_TARGET_CXXFLAGS config option and set it by default to -fno-exceptions.

Add `CT_LIBC_PICOLIBC_GCC_LIBSTDCXX_TARGET_CXXFLAGS` config option and
set it by default to '-fno-exceptions'.

Signed-off-by: Adrian Gielniewski <[email protected]>
config LIBC_PICOLIBC_GCC_LIBSTDCXX_TARGET_CXXFLAGS
string
prompt "Target CXXFLAGS for libstdc++ picolibc variant"
default "-fno-exceptions"
Copy link

@Damian-Nordic Damian-Nordic Feb 27, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a thought, would it make sense to use this default for ARM thumb only? I can see some samples in Zephyr that enable CPP_EXCEPTIONS so would probably be good to be able to still run them on some qemu targets.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, I found it. I think it would be the best to have the same configuration for all targets.

@adigie adigie marked this pull request as draft May 15, 2025 08:11
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.

3 participants