diff options
| author |  bors[bot] <bors[bot]@users.noreply.github.com>
| 2018-08-12 14:39:00 +0000 |
|---|---|---|
| committer | bors[bot] <bors[bot]@users.noreply.github.com>
| 2018-08-12 14:39:00 +0000 |
| commit | 96b76f974a7de4423f5bb0f529b399b0e310be2a (patch) | |
| tree | 22068890759b65d96e41a39fab5869a1f77e630c /cortex-m-rt/examples/pre_init.rs | |
| parent | 230d42233d35f13de82c1c7cb893352512ed3794 (diff) | |
| parent | 97b184df173a56287e34841f0115a1e5823d1aa1 (diff) | |
| download | cortex-m-96b76f974a7de4423f5bb0f529b399b0e310be2a.tar.gz cortex-m-96b76f974a7de4423f5bb0f529b399b0e310be2a.tar.zst cortex-m-96b76f974a7de4423f5bb0f529b399b0e310be2a.zip | |
Merge #87
87: Update linker script to put .data into FLASH r=japaric a=adamgreig
This is the updated linker script and test from #86.
Sadly it looks like LLD does not use the `ALIGN(4)` in the `.data` section header to align the LMA (unlike gcc), so we still need the `. = ALIGN(4)` at the end of `.rodata` to ensure LMA alignment.
I've added a failing example which the ci script ensures fails when `.data` causes overflow. It just checks for non-zero return from cargo rather than specifically grepping for the linker error messages about `.data` overflowing; since we only have the one failing example I could remove the loop and just specifically check it and grep for the relevant error from gcc and lld if people think that would be better.
Co-authored-by: Adam Greig <adam@adamgreig.com>
Co-authored-by: Jorge Aparicio <jorge@japaric.io>
Diffstat (limited to 'cortex-m-rt/examples/pre_init.rs')
0 files changed, 0 insertions, 0 deletions