Skip to content

Commit

Permalink
crosstool-ng: Update to pull in libstdc++ nano config fix
Browse files Browse the repository at this point in the history 
Update build script to pull in the crosstool-ng commit that corrects
the build specs for the libstdc++ nano, which is used with newlib-nano.

For more details, refer to the issue #346.

Signed-off-by: Stephanos Ioannidis <root@stephanos.io>
  • Loading branch information
@stephanosio @galak
stephanosio authored and galak committed Jun 16, 2021
1 parent bbd41c9 commit fd4d880
Showing 1 changed file with 3 additions and 0 deletions.
3 changes: 3 additions & 0 deletions release-notes.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,9 @@

- gcc:
* Removed libgcc transactional memory clone registry support
* Fixed incorrect build specs for libstdc++ nano variant. The libstdc++ nano
variant, which is used with newlib-nano, is now built with
`-fno-exceptions` to reduce compiled binary size.

## Zephyr SDK 0.13.0-alpha-1

Expand Down

1 comment on commit fd4d880

@johngrey-dev
Copy link

Choose a reason for hiding this comment

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

Hi.
Why disable exceptions in nano altogether?
exceptions is a pretty heavy feature to just remove, where the previous libstdc++ is too large for some targets, libc-nano with exceptions was the perfect fit for embedded apps with exceptions.

Why not have the 3 variants (no covid pun intended) ?
Full libc, libc-nano with exceptions & minimal libc-nano. Then have use CONFIG_EXCEPTIONS and CONFIG_NEWLIB_LIBC_NANO point to the desired one at link?

I can open an issue + PR for this if it can interest the community.

Please sign in to comment.