diff options
| author |  bors[bot] <26634292+bors[bot]@users.noreply.github.com>
| 2020-08-29 11:31:50 +0000 |
|---|---|---|
| committer |  GitHub <noreply@github.com>
| 2020-08-29 11:31:50 +0000 |
| commit | 97ad3685d82cab3582602a1d044e80bc3edaaab6 (patch) | |
| tree | c26c4a4b099123d4142a9c88479fd9d5fa7b3d54 /cortex-m-rt/examples/device.rs | |
| parent | 8a165d9a45cecd551b115dc52ed5b1bdc77f4af1 (diff) | |
| parent | 49a68f13d8d22cad02004e4c90559345b225ce26 (diff) | |
| download | cortex-m-97ad3685d82cab3582602a1d044e80bc3edaaab6.tar.gz cortex-m-97ad3685d82cab3582602a1d044e80bc3edaaab6.tar.zst cortex-m-97ad3685d82cab3582602a1d044e80bc3edaaab6.zip | |
Merge #287
287: Fix common uses of INSERT AFTER with .bss and .text r=adamgreig a=mattico
Fixes #267
Fixes #266
This fixes two related issues.
1. Named sections are often inserted after `.bss` or `.text` in order to have them handled as if they were part of that section. Defining the start/end symbols outside of the section allows this to work.
2. Uninitialized C statics will end up as common symbols which end up in the COMMON input section. If this section is orphaned, it will likely end up placed after `.bss`. C code often expects these statics to be zero initialized. The first change would cause these symbols to be placed before `__ebss` so they will get zeroed by the reset handler. Explicitly placing the common symbols into `.bss` ensures this happens. Users who want uninitialized symbols should use the `.uninit` section.
See https://github.com/rust-embedded/cortex-m-rt/pull/287#issuecomment-677743856
Co-authored-by: Matt Ickstadt <mattico8@gmail.com>
Diffstat (limited to 'cortex-m-rt/examples/device.rs')
0 files changed, 0 insertions, 0 deletions