aboutsummaryrefslogtreecommitdiff
path: root/cortex-m-rt/check-blobs.sh
diff options
context:
space:
mode:
authorGravatar bors[bot] <26634292+bors[bot]@users.noreply.github.com> 2021-01-27 13:22:26 +0000
committerGravatar GitHub <noreply@github.com> 2021-01-27 13:22:26 +0000
commit7b27817237cf22d1b92f3638d546dacf60d2a97d (patch)
tree8aa463a93a2f9a2a8e07cd97278ed6df85f5fb96 /cortex-m-rt/check-blobs.sh
parent8a64815108bf266e97a82c9be89bbc2ccbf0a5c3 (diff)
parentf0e2218330adcffe7dc8a05869dac0e5399058c3 (diff)
downloadcortex-m-7b27817237cf22d1b92f3638d546dacf60d2a97d.tar.gz
cortex-m-7b27817237cf22d1b92f3638d546dacf60d2a97d.tar.zst
cortex-m-7b27817237cf22d1b92f3638d546dacf60d2a97d.zip
Merge #310
310: Only emit link_section for cortex-m r=jonas-schievink a=adamgreig Previously we always emitted `link_section`, even though it only had an effect when our linker script was being used (and only made sense on cortex-m targets). This breaks building the code for a MacOS target, which is occasionally useful for running `cargo check` etc. In the macros crate we don't have the target information available, so instead we continue to emit `link_section` except specifically on MacOS. This keeps the fix from #306 but hopefully resolves the confusion in https://github.com/rust-embedded/cortex-m-rt/issues/74#issuecomment-768079657. Co-authored-by: Adam Greig <adam@adamgreig.com>
Diffstat (limited to 'cortex-m-rt/check-blobs.sh')
0 files changed, 0 insertions, 0 deletions