You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On small systems (e.g. Cortex-M4) every KB of code footprint counts, and the OID name and description string tend to only be needed in certain debugging/tools contexts (e.g. mbedtls_x509_crt_info()). I've noticed that when building with -ffunction-sections, -fdata-sections, and gc-sections, there are a few KB of wasted code space because constant strings are entangled to types in a way that makes it hard for a linker to omit them.
I have a similar approach in mind as Mbed-TLS/mbedtls#2315, and propose the configuration MBEDTLS_OID_NAMES. If you agree I can get started on the PR.
Note that because mbed TLS now uses mbed-crypto, this issue is a dependency for that PR.
Issue request type
[ ] Question
[X] Enhancement
[ ] Bug
The text was updated successfully, but these errors were encountered:
Description
On small systems (e.g. Cortex-M4) every KB of code footprint counts, and the OID name and description string tend to only be needed in certain debugging/tools contexts (e.g.
mbedtls_x509_crt_info()
). I've noticed that when building with-ffunction-sections
,-fdata-sections
, andgc-sections
, there are a few KB of wasted code space because constant strings are entangled to types in a way that makes it hard for a linker to omit them.I have a similar approach in mind as Mbed-TLS/mbedtls#2315, and propose the configuration
MBEDTLS_OID_NAMES
. If you agree I can get started on the PR.Note that because mbed TLS now uses mbed-crypto, this issue is a dependency for that PR.
Issue request type
The text was updated successfully, but these errors were encountered: