-
Notifications
You must be signed in to change notification settings - Fork 3k
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
STM32: Fix alignment of execute region to 8byte boundary #8013
Conversation
Nope, this is only fixing a very small subset of targets. It's no good, you must fix ALL of them. |
Please share which targets are failing, we do not support ARMC6 for all v6/v7 targets. |
1848571
to
a8ec28c
Compare
Fix is for all ST targets |
Hi @ARMmbed/team-st-mcd |
mbed-os/targets/TARGET_STM/TARGET_STM32L4/TARGET_STM32L496xG/device/TOOLCHAIN_IAR/stm32l496xx.icf Line 10 in 48c149b
I like comment "428 = 53 x 8" ... |
a8ec28c
to
304e358
Compare
@jeromecoutant IAR and GCC files are updated. Please review |
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.
I'm ok with the changes.
Would be just great to add a few words in the commit messages themselves, basically a kind of copy of #8004 description that explains that been breaking change when removing --legacyalign compile option (or at least this is my understanding ..)
@@ -35,8 +35,8 @@ LR_IROM1 0x08000000 0x20000 { ; load region size_region (128K) | |||
.ANY (+RO) | |||
} | |||
|
|||
; 59 vectors (16 core + 43 peripheral) * 4 bytes = 236 bytes to reserve (0xEC) | |||
RW_IRAM1 (0x20000000+0xEC) (0x5000-0xEC) { ; RW data | |||
; 59 vectors (16 core + 43 peripheral) * 4 bytes = 236 bytes to reserve (0xEC+0x4) |
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.
please add a comment that says +0x04 says it's for overall 8 bytes alignment
ce1df12
to
a44ccf1
Compare
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.
OK for me. It seems this PR is only for STM32 devices, so maybe add "STM32:" in the PR title ?
We should do the rest of the chips as well, not just STM (just my humble opinion). This is a quite large change - it's trivial, but amount of files modified is quite large. My 1st scan on this (when I stated there's more than >250 files impacted) missed actually quite a few files... |
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.
ST CI tests OK
/morph build |
Build : SUCCESSBuild number : 3196 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 2788 |
Test : FAILUREBuild number : 2996 |
The test failure not related to this changeset, we will restart after 5.10.1 RC is completed |
/morph build |
Test : FAILUREBuild number : 3102 |
Stopped job because it's consistently failing against NUCLEO_F207ZG. |
From the changes, I do not see why it would fail @ARMmbed/team-st-mcd any pointers? |
…r files --legacyalign, --no_legacyalign are deprecated from ARMC6 compiler, in order to remove deprecated flags all linker files should strictly align to 8-byte boundary
1970647
to
bf1a2c8
Compare
-/* 8-byte aligned(0x184) = 0x188 |
/morph build |
Build : SUCCESSBuild number : 3301 Triggering tests/morph test |
Exporter Build : SUCCESSBuild number : 2936 |
Test : SUCCESSBuild number : 3110 |
#8024 supercedes this PR. |
Adding label back in. Not convinced this isn't an ordering issue. |
Mmm can't see why this won't automatically apply to the release. Will try manually patching this when all others have gone in... |
Description
Resolves #8004
Pull request type