IAR build fixes before 1.1.0/4.1.0/3.6.6: framework support #289
No reviewers
Labels
No labels
approved
bug
dependencies
DO-NOT-MERGE
enhancement
good-first-issue
help-wanted
historical-reviewed
historical-reviewing
needs-adoption
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
single-reviewer
size-l
size-m
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/mbedtls-framework!289
Loading…
Reference in a new issue
No description provided.
Delete branch "iar-1.1.0-framework"
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 the build of the library and the unit tests with IAR.
Also fix a problem with the structure of test helper code that I introduced in https://github.com/Mbed-TLS/mbedtls-framework/pull/279 and which is causing me a problem in a security fix: part of
test_common.hshould have been intests/src, nottests/include/test.PR checklist
Pull request overview
This PR fixes IAR build issues for the library/unit tests by restructuring test build-configuration includes and adding IAR-specific compatibility knobs in the test harness.
Changes:
tests/include/test/build_info.hand switch test headers to include it (instead oftest_common.h) for consistent build configuration and private-access support.tests/src/test_common.hand ensure test.cfiles include it first.Reviewed changes
Copilot reviewed 31 out of 31 changed files in this pull request and generated no comments.
Show a summary per file
test_common.hfirst for consistent compiler/test setup.test_common.hfirst for consistent compiler/test setup._DLIB_FILE_DESCRIPTORdefine; includetest/build_info.hfor test build config.test_common.hfirst for consistent compiler/test setup.test_common.hfirst for consistent compiler/test setup.test_common.h; suppress an IAR-specific diagnostic.test_common.hfirst for consistent compiler/test setup.test_common.hfirst for consistent compiler/test setup.test_common.hfirst for consistent compiler/test setup.test_common.hfirst for consistent compiler/test setup.test_common.hfirst for consistent compiler/test setup.test_common.hinclude.test_common.hfirst for consistent compiler/test setup.test_common.hfirst for consistent compiler/test setup.build_info.h(test header build config).build_info.h(test header build config).build_info.h(test header build config).build_info.h(test header build config).build_info.h(test header build config).build_info.h(test header build config).build_info.h(test header build config).build_info.h(test header build config).build_info.h(test header build config).build_info.h(test header build config).build_info.h(test header build config).build_info.h(test header build config).build_info.h(test header build config).build_info.h(test header build config).build_info.h(test header build config).build_info.h(test header build config).💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
The only current failure on the CI (
DTLS proxy: 3d, gnutls client, fragmentation, nbio=2) looks spurious and changes look good to me, so I approveI've restarted the CI since we want to see it pass.
Can this be changed to a push/pop or restore instead of a pragma, or is it required to cover the whole file?
I'd use it for the whole file anyway (I'm ignoring the warning because it's a common idiom, if it was just in one place I'd refactor that one place).
But anyway, does IAR have push/pop for
#pragma diag_xxx? I can't find it in the manual.OK, fair enough. Just wanted to check it had been considered. I'll close this one.
Looks good as long as we can get the CI to pass.