-
Notifications
You must be signed in to change notification settings - Fork 3k
iar - fix flags for cmd and exporters #1948
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
Conversation
@mbed-bot: TEST HOST_OSES=windows |
[Build 483] |
@mbed-bot: TEST HOST_OSES=windows |
[Build 484] |
@mbed-bot: TEST HOST_OSES=windows |
Test 484 looks good. I tested this on some examples within This patch fixes in this repo IAR projects (they would not compile as some flags were not compatible). Please review |
[Build 487] |
It seems M7 has some weird hiccups, investigating. |
Exporters and cmd do not share all flags, some asm and c flags are not the same (cpu, fpu)
@mbed-bot: TEST HOST_OSES=windows |
[Build 493] |
Cortex-M7 problem corrected (if anyone ever gets Return 3 error from IAR , look at how you are passing arguments, in my case "[--cpu mode]" was failing, had to be ["--cpu", "mode"]), tests results look good. |
👍 |
- creating new core name Cortex_M7F_DP for a target with a double precision fpu - adding new core name to arm.py to set compiler/linker flags to a double precision fpu when configured in target.json - up to now: gcc wrote flag for a double precision fpu -> target with STM32F746 didn't run when using double variables - mcu has only single precision fpu - changing gcc.py to use single precision for Cortex-M7 und double precision for Cortex_M7F_DP tested with NUCLEO_F746, NUCLEO_F767 and build.py+make.py and exporting with project.py + compiling/flashing - iar.py need a similar extention - I didn't change that yet because - did not run at the moment - python exception - currently worked on in PR ARMmbed#1948
- creating new core name Cortex_M7F_DP for a target with a double precision fpu - adding new core name to arm.py to set compiler/linker flags to a double precision fpu when configured in target.json - up to now: gcc wrote flag for a double precision fpu -> target with STM32F746 didn't run when using double variables - mcu has only single precision fpu - changing gcc.py to use single precision for Cortex-M7 und double precision for Cortex_M7F_DP tested with NUCLEO_F746, NUCLEO_F767 and build.py+make.py and exporting with project.py + compiling/flashing - iar.py need a similar extention - I didn't change that yet because - did not run at the moment - python exception - currently worked on in PR ARMmbed#1948
- creating new core name Cortex_M7F_DP for a target with a double precision fpu - adding new core name to arm.py to set compiler/linker flags to a double precision fpu when configured in target.json - up to now: gcc wrote flag for a double precision fpu -> target with STM32F746 didn't run when using double variables - mcu has only single precision fpu - changing gcc.py to use single precision for Cortex-M7 und double precision for Cortex_M7F_DP tested with NUCLEO_F746, NUCLEO_F767 and build.py+make.py and exporting with project.py + compiling/flashing - iar.py need a similar extention - I didn't change that yet because - did not run at the moment - python exception - currently worked on in PR ARMmbed#1948
Exporters and cmd do not share all flags, some asm and c flags are not the same (cpu, fpu).
This is the clean up of the latest changes, that made some changes not available for cmd or exporters.
The changeset applied to mbed lib:
After the change:
C file
C++ file
asm file
I am still running some local test, going to compare sizes of executables within make.py and project.py, to be sure flags are 1:1 as they used to be (more than 1 week ago when the consolidation of flags happened).
@sg- @bridadan @screamerbg