Add debug symbols to release builds

[0xc0170]

Replaces #2139, adding more flags for ARMCC to make the output smaller, now it should be 2x bigger than usual (more info in the referenced pull request).

All toolchains now produces output folders with acceptable sizes. Please review

@bogdanm @sg- @meriac @bridadan @screamerbg

[0xc0170]

/morph test

[bogdanm]

👍

[screamerbg]

Until the ARMCC huge size issues are resolved I can't endorse this, sorry. mbed library releases will be HUGE (200mb+ per target). Hence I think this should be switch to -o, e.g. mbed compile ... -o debug-symbols

@sg- @0xc0170

[screamerbg]

Additionally, there should be a way to tell the build tools not to include the debug symbols, e.g. this patch makes it mandatory.

[mbed-bot]

Result: SUCCESS

Your command has finished executing! Here's what you wrote!

/morph test

Output

mbed Build Number: 900

All builds and test passed!

[0xc0170]

Until the ARMCC huge size issues are resolved I can't endorse this, sorry. mbed library releases will be HUGE (200mb+ per target). Hence I think this should be switch to -o, e.g. mbed compile ... -o debug-symbols

that does not sound correct, I have been testing this patch locally, I provided numbers in the earlier PR, that this does not increase size 10x as it was (-g), but for ARMCC the size increase is around ~2x. Here're mbed-os-example-blinky numbers: #2139 (comment)

mbed-lib (using python tools/build.py -m K64F -t ARM)
k64f ARM:

• 5MB without --debug
• 7MB with "--debug", "--dwarf3", "--no_debug_macros", "--remove_unneeded_entities"

nucle f411re ARM:

• 4MB without --debug
• 8MB "--debug", "--dwarf3", "--no_debug_macros", "--remove_unneeded_entities"

Additionally, there should be a way to tell the build tools not to include the debug symbols, e.g. this patch makes it mandatory.

What's the use case? the size of output is not that different, thus I don't think we need one more option for this to disable. I wouldn't want option for everything if really not required.

[meriac]

@screamerbg I agree with @0xc0170 - I would not add an option to suppress debug information as it will be required for our build time statics and the overhead is negligible. If someone needs that for confidentiality reasons, they can still run *-strip over the resulting elf file (which happens after outputting the statistics).

[bridadan]

@mbed-bot: TEST

HOST_OSES=ALL
BUILD_TOOLCHAINS=ALL
TARGETS=ALL

[bridadan]

I kicked off a test to see how it performs. I will be monitoring the CI machine just in case the size starts to explode.

[0xc0170]

One consideration would be the mbed-sdk releases and how mbed online IDE can handle this increase in size.

[screamerbg]

@0xc0170 can you provide numbers/sizes with the current flags, e.g. no debug

[0xc0170]

@0xc0170 can you provide numbers/sizes with the current flags, e.g. no debug

The comment above, for K64F and NUCLEO F411RE build mbed lib with and without debug flags for ARMCC, paste here again:

mbed-lib (using python tools/build.py -m K64F -t ARM)
k64f ARM:

• 5MB without --debug
• 7MB with "--debug", "--dwarf3", "--no_debug_macros", "--remove_unneeded_entities"

nucleo f411re ARM:

• 4MB without --debug
• 8MB "--debug", "--dwarf3", "--no_debug_macros", "--remove_unneeded_entities"

[mbed-bot]

[Build 951]
SUCCESS: Building succeeded and tests were run! Be sure to check the test results

[sg-]

We are planning to introduce compile profiles and this change can be introduced then.

[sg-]

@0xc0170 profile support PR is up. Lets get this effort reflected over on #2802