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
Nit: I'd find it clearer if there was a blank line after the RUN lines before the SKIP-EMPTY lines.
Aside: I'm slightly surprised this works, given that -EMPTY is also a FileCheck suffix!