a651607b37
Some preprocessor macro definitions must have a specific expansion so that the same macro name can be defined in different products. The definition of having the same expansion (per the C language specification) means the same sequence of tokens, and also the same absence/presence of spacing between tokens. Two macros are also defined in headers in the PSA Compliance test suite, so the test suite would fail to build if we changed the definitions. Preserve those definitions. Technically this is a bug in the test suite, since having extra spaces (or even a completely different constant expression with the same value) would still be compliant. Bug reported as https://github.com/ARM-software/psa-arch-tests/issues/337 Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com> |
||
|---|---|---|
| .. | ||
| crypto.h | ||
| crypto_builtin_composites.h | ||
| crypto_builtin_primitives.h | ||
| crypto_compat.h | ||
| crypto_config.h | ||
| crypto_driver_common.h | ||
| crypto_driver_contexts_composites.h | ||
| crypto_driver_contexts_primitives.h | ||
| crypto_extra.h | ||
| crypto_platform.h | ||
| crypto_se_driver.h | ||
| crypto_sizes.h | ||
| crypto_struct.h | ||
| crypto_types.h | ||
| crypto_values.h | ||