From dcc0ee1a1ebe094627db34c08a7362ac69febad5 Mon Sep 17 00:00:00 2001 From: Tom Cosgrove Date: Tue, 21 Mar 2023 15:44:16 +0000 Subject: [PATCH] Update changelog entry, splitting into two sections Signed-off-by: Tom Cosgrove --- ChangeLog.d/reduce-cpu-modifiers-to-file-scope.txt | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/ChangeLog.d/reduce-cpu-modifiers-to-file-scope.txt b/ChangeLog.d/reduce-cpu-modifiers-to-file-scope.txt index bb8d2a289..9bfc80c99 100644 --- a/ChangeLog.d/reduce-cpu-modifiers-to-file-scope.txt +++ b/ChangeLog.d/reduce-cpu-modifiers-to-file-scope.txt @@ -1,4 +1,12 @@ Bugfix - * Fix #5758. Compilers might generate unexpected instructions when CPU - modifiers were specified as global flags( command line or global headers). - It is fixed with reducing the scope of CPU modifier flags. + * Fix an issue when compiling with MBEDTLS_SHA512_USE_A64_CRYPTO_IF_PRESENT + enabled, which required specifying compiler flags enabling SHA3 Crypto + Extensions, where some compilers would emit EOR3 instructions in other + modules, which would then fail if run on a CPU without the SHA3 + extensions. Fixes #5758. + +Changes + * When enabling MBEDTLS_SHA256_USE_A64_CRYPTO_* or + MBEDTLS_SHA512_USE_A64_CRYPTO_*, it is no longer necessary to specify + compiler target flags on the command line; the library now sets target + options within the appropriate modules.