Fix AESCE regression with Clang due to inclusion order changes #603
No reviewers
Labels
No labels
api-break
approved
bug
component-docs
component-platform
component-test
dependencies
deprecation
DO-NOT-MERGE
enhancement
good first issue
help wanted
needs-adoption
needs-backports
needs-ci
needs-design-approval
needs-info
needs-preceding-pr
needs-review
needs-reviewer
needs-work
priority-high
priority-low
priority-medium
priority-scheduled
priority-very-high
resolved-after-1.1
single-reviewer
size-l
size-m
size-optimisation
size-s
size-xs
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-Mbed-TLS/TF-PSA-Crypto!603
Loading…
Reference in a new issue
No description provided.
Delete branch "include-common-first-fix-aesce"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fix https://github.com/Mbed-TLS/TF-PSA-Crypto/issues/601, a regression introduced by https://github.com/Mbed-TLS/TF-PSA-Crypto/pull/550 which just got merged.
PR checklist
clang-15 -target aarch64-linux-gnu --sysroot /usr/aarch64-linux-gnu -I include -I core -I drivers/builtin/include -c drivers/builtin/src/aesce.c(see the issue description for more details). I tested locally as far back as clang 7. Clang 6 and earlier have a different problem: https://github.com/Mbed-TLS/TF-PSA-Crypto/issues/604I'm adding this issue to the 1.1/4.1 LTS board, not because it particularly has to be done before the LTS, but because if we don't merge this, we'll have a regression compared to 1.0. So it's a “should be done before the next minor release” thing, not a “should be done before the next LTS release.”
LGTM, thanks!