-
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
Remove duplicate pop from MPU Wrappers ASM Files #1008
Remove duplicate pop from MPU Wrappers ASM Files #1008
Conversation
…able/GCC/ARM_CM23/mpu_wrappers_v2_asm.c
…able/GCC/ARM_CM23_NTZ/mpu_wrappers_v2_asm.c
…able/GCC/ARM_CM33/mpu_wrappers_v2_asm.c
…able/GCC/ARM_CM33_NTZ/mpu_wrappers_v2_asm.c
…able/IAR/ARM_CM23/mpu_wrappers_v2_asm.S
…able/IAR/ARM_CM23_NTZ/mpu_wrappers_v2_asm.S
…able/IAR/ARM_CM33/mpu_wrappers_v2_asm.S
…able/IAR/ARM_CM33_NTZ/mpu_wrappers_v2_asm.S
… duplicate pop instruction in mpu_wrappers_v2_asm
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1008 +/- ##
=======================================
Coverage 93.00% 93.00%
=======================================
Files 6 6
Lines 3200 3200
Branches 879 879
=======================================
Hits 2976 2976
Misses 111 111
Partials 113 113
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Quality Gate passedIssues Measures |
….(32bit/64bit) (FreeRTOS#1199) * [WIN32-MingW Demo] Add tick type width definition based on compiler type.(32bit/64bit) 32bit TickType_t is used if compiler is MinGW32. 64bit TickType_t is used if compiler is MinGW64. Reason of change: Before this change, 32bit TickType_t is always used in MinGW demo. It is inefficient for 64bit compiler. In addition, MinGW64 reported warnings for the cast operation between TickType_t and (void *) pointer because of different width. 64bit TickType_t should be used instead of 32bit if compiler is 64bit. * [WIN32-MingW Demo] Change printf() format specifiers from %u to %llu. Reason of change: %u specifier corrupts 64bit tick count because it supports only 32bit value. %llu can be used for both of 64bit value and 32bit value.(After casting to 64bit) * [WIN32-MingW Demo] Change type of some variables from uint32_t to UBaseType_t. Reason of change: These variables are cast to/from pointer type in existing codes. 64bit compiler(MinGW64) reports warnings for the cast operations between uint32_t and pointer type. UBaseType_t solves those warnings because it has same width as pointer type on both of MinGW32 and MinGW64. * [WIN32-MingW Demo] Change type of some variables from uint32_t to UBaseType_t. Same change as previous commit is applied to source codes which are built only on Debug configuration. * [WIN32-MingW Demo] Add brackets to the condition in #if statement. Behavior is not changed. Reason of change is to follow coding style guide of FreeRTOS. * Update "FreeRTOS/Source" submodule(FreeRTOS-kernel) to FreeRTOS#1008. * [WIN32-MingW Demo] Change type of one more variable from uint32_t to UBaseType_t. Additional modification for solving compiler warnings for the cast operation on MinGW64. * Update FreeRTOS-kernel submodule version in manifest.yml. * Modify prefix of variables to follow coding style guide. * Code review suggestions Signed-off-by: Gaurav Aggarwal <[email protected]> --------- Signed-off-by: Gaurav Aggarwal <[email protected]> Co-authored-by: ActoryOu <[email protected]> Co-authored-by: Gaurav-Aggarwal-AWS <[email protected]> Co-authored-by: Gaurav Aggarwal <[email protected]>
Description
In the MPU Wrappers functions registers are pushed to determine if the CPU is operating in a privileged mode
These registers are currently restored after the branch instruction, leading to a duplicate
pop
instruction being placed into each MPU wrapper function.This PR moves the pop to be before the branch is taken, removing the duplicate instruction.
Test Steps
Checklist:
Related Issue
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.