Google Git
Sign in
pigweed/third_party/github/Mbed-TLS/mbedtls-framework/0c94e7d16454e9501f9bb5f19ae8ff551e279e2c
commit
0c94e7d16454e9501f9bb5f19ae8ff551e279e2c
[log]
author
Gilles Peskine <Gilles.Peskine@arm.com>
Thu Jan 15 19:25:53 2026 +0100
committer
Gilles Peskine <Gilles.Peskine@arm.com>
Thu Jan 15 19:31:27 2026 +0100
tree
6402222106d1ec35e8a55121dd084041aff030d0
parent
dd06b4989f86c47bc7f877068d51d66a131fefd4 [diff]
check_names: Allow mldsa-native symbols to be undeclared

The mldsa-native and mlkem-native headers use preprocessor tricks to
construct identifiers. We can't recognize those. So f a symbol found in the
binary is in the expected sub-namespace for those parts of the library,
allow it to be undeclared.

Make the exception general enough for mldsa-native (needed now) and
mlkem-native (needed soon).

Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
1 file changed
tree: 6402222106d1ec35e8a55121dd084041aff030d0
  1. .github/
  2. data_files/
  3. docs/
  4. history/
  5. psasim/
  6. scripts/
  7. tests/
  8. .gitignore
  9. CMakeLists.txt
  10. CONTRIBUTING.md
  11. dco.txt
  12. exported.make
  13. LICENSE
  14. README.md
README.md

Mbed TLS framework

This repository contains a version-independent build and test framework for TF-PSA-Crypto and Mbed TLS.

You need this repository as a Git submodule in a branch of one of the above repositories if:

  • You want to build, test or contribute to Mbed TLS 3.6.0 or above, and you are working from a snapshot of a Git commit on a development branch.
  • You want to build, test or contribute to TF-PSA-Crypto, and you are working from a snapshot of a Git commit on a development branch.

You do not need this repository if:

  • You are working with Mbed TLS 2.28.
  • You want to build a release of Mbed TLS and run its unit tests.

Contributing

We gratefully accept bug reports and contributions from the community. Please see the contributing guidelines for details on how to do this.

License

Unless specifically indicated otherwise in a file, Mbed TLS framework files are provided under a dual Apache-2.0 OR GPL-2.0-or-later license. See the LICENSE file for the full text of these licenses, and the ‘License and Copyright’ section in the contributing guidelines for more information.