Add MBED_SECTION attribute

[c1728p9]

Allow the section that code is placed in to be explicitly specified with the attribute MBED_SECTION.

[c1728p9]

@mbed-bot: TEST

[c1728p9]

/morph test

[bridadan]

@mbed-bot: TEST

HOST_OSES=ALL
BUILD_TOOLCHAINS=ALL
TARGETS=ALL

[mbed-bot]

Result: SUCCESS

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

/morph test

Output

mbed Build Number: 1488

All builds and test passed!

[mbed-bot]

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

[geky]

Not to be a stickler, but this should come in with a test for compiler support
https://github.com/ARMmbed/mbed-os/tree/master/TESTS/mbedmicro-mbed/attributes

[c1728p9]

Since there is no guarantee on section names by the current linker files in the code base I can't think of a good way to test this. When bootloader support comes it will test this. Furthermore if linker script generation with named sections becomes a thing this will be easily testable. If you can think of a clean way to test this in its current form then I would be glad to add tests.

[geky]

Ah interesting, fair enough, go for it 👍

[pan-]

@c1728p9 What is the use case of this extension for the end user if it is not possible to provide custom linker script ? Is it for internal mbed-os internal use only ?

[c1728p9]

@pan- this feature will be used by the bootloader to put data in a dedicated no-init ram region. It is possible to specify a custom linker script from the command line if someone want to use it for another purpose though.

[theotherjimmy]

@pan- Basically

if it is not possible to provide custom linker script ?

It is possible

  -l LINKER_SCRIPT, --linker LINKER_SCRIPT
                        use the specified linker script

[pan-]

@c1728p9 @theotherjimmy Thanks for the clarification. There's something I've missed apparently 😆 .