diff options
| author | Fangrui Song <maskray@google.com> | 2020-04-30 22:15:05 -0700 |
|---|---|---|
| committer | Fangrui Song <maskray@google.com> | 2020-05-01 20:42:53 -0700 |
| commit | d4d4c6bf834142326301a743d2939e868d9f0f0f (patch) | |
| tree | c19309f9901f39d2f7cc196caccbcb2678ed29a6 /llvm/test/CodeGen/ARM/debug-segmented-stacks.ll | |
| parent | 060f2f815c4d337f6a1ed9d582a8583b7ed9135e (diff) | |
| download | bcm5719-llvm-d4d4c6bf834142326301a743d2939e868d9f0f0f.tar.gz bcm5719-llvm-d4d4c6bf834142326301a743d2939e868d9f0f0f.zip | |
[llvm-objcopy] -O binary: skip empty sections
After SHF_ALLOC sections are ordered by LMA:
* If initial sections are empty, GNU objcopy skips their contents while we
emit leading zeros. (binary-paddr.test %t4)
* If trailing sections are empty, GNU objcopy skips their contents while we
emit trailing zeros. (binary-paddr.test %t5)
This patch matches GNU objcopy's behavior. Linkers don't keep p_memsz
PT_LOAD segments. Such empty sections would not have a containing
PT_LOAD and `Section::ParentSegment` might be null if linkers fail to
optimize the file offsets (lld D79254).
In particular, without D79254, the arm Linux kernel's multi_v5_defconfig
depends on this behavior: in `vmlinux`, an empty .text_itcm is mapped at
a very high address (0xfffe0000) but the kernel does not expect
`objcopy -O binary` to create a very large `arch/arm/boot/Image`
(0xfffe0000-0xc0000000 ~= 1GiB). See https://bugs.llvm.org/show_bug.cgi?id=45632
Reviewed By: jhenderson
Differential Revision: https://reviews.llvm.org/D79229
(cherry picked from commit ec786906f5feb4dceba1b5338927079e63e78095)
Diffstat (limited to 'llvm/test/CodeGen/ARM/debug-segmented-stacks.ll')
0 files changed, 0 insertions, 0 deletions

