Develop.json - optimize on size rather than performance #5274
Conversation
The profiles must now have different optimization targets, if customer assumes the tests done with develop are the same as with release profile (sans the debugs) - they would be assuming wrongly. The code can behave unfortunately very differently if one is optimizing for size and one for performance. If customer wants to optimize for performance, they should change it to both profiles so that any tests done with develop and release match as closely as possible. This change impacts both IAR and ARM CC. - ARM and uARM were optimizing on time in release profile. - IAR was optimizing on "High, balaned" in develop profile. GCC is defined to behave logically between these profiles (-Os).
|
cc @sg- @theotherjimmy @kjbracey-arm |
|
Similar discussion already in #2600. This is considered being a breaking change (changining the default profile). |
|
Why do we keep revisiting this...
If you read the PR conversation as to why this was changed (I've very much disagreed with) it was to "make client fit in 512k block for K64F" which never should have happened and is not precedent for this type of a change. The profiles have different optimization levels by design. Why not propose that release profile optimizes for speed with logs removed? |
Build : SUCCESSBuild number : 12 |
|
@JanneKiiskila Please read the comments above. retest uvisor |
|
@JanneKiiskila any update on this after @sg- comments ? |
Description
The profiles must now have different optimization targets,
if customer assumes the tests done with develop are the same
as with release profile (sans the debugs) - they would be assuming
wrongly. The code can behave unfortunately very differently if one
is optimizing for size and one for performance.
If customer wants to optimize for performance, they should change
it to both profiles so that any tests done with develop and release
match as closely as possible.
This change impacts both IAR and ARM CC.
GCC is defined to behave logically between these profiles (-Os).
Status
READY
Migrations
NO