-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update the memory alignment within the Cortex-A9 port asm code #426
Update the memory alignment within the Cortex-A9 port asm code #426
Conversation
…to update-cortex-a9-alignment
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #426 +/- ##
=======================================
Coverage 93.78% 93.78%
=======================================
Files 6 6
Lines 3184 3184
Branches 885 885
=======================================
Hits 2986 2986
Misses 91 91
Partials 107 107
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Re-verify the ARM_CA9 port on zynq board without problem.
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Update alignment in ARM_CR5 port. This is the same patch as 553caa1 provided by Richard Barry for issue FreeRTOS#426 (ARM_CA9). Signed-off-by: Florian La Roche <Florian.LaRoche@gmail.com>
Description
Update the assembly code used in the Cortex-A9 port to ensure stack alignment before calling vTaskSwitchContext() in case user code added to the function (maybe via a trace macro or other mechanism) requires the more strict alignment. That would be the case if, as an example, floating point instructions were used.
Test Steps
The self monitoring integration tests have been running for several weeks with no issues.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.