summaryrefslogtreecommitdiffstats
path: root/libcxx/include/algorithm
diff options
context:
space:
mode:
authorJake Ehrlich <jakehehrlich@google.com>2018-01-22 19:27:30 +0000
committerJake Ehrlich <jakehehrlich@google.com>2018-01-22 19:27:30 +0000
commit46814bee63480b7bd891a66821f9946575832aed (patch)
tree160625192f621e1211da1bf12b81d28f04c77e28 /libcxx/include/algorithm
parent98bb420559f76d53d5daffd948e561e75dd29fe9 (diff)
downloadbcm5719-llvm-46814bee63480b7bd891a66821f9946575832aed.tar.gz
bcm5719-llvm-46814bee63480b7bd891a66821f9946575832aed.zip
[llvm-objcopy] Use physical instead of virtual address when aligning and placing sections in binary
For sections with different virtual and physical addresses, alignment and placement in the output binary should be based on the physical address. Ran into this problem with a bare metal ARM project where llvm-objcopy added a lot of zero-padding before the .data section that had differing addresses. GNU objcopy did not add the padding, and after this fix, neither does llvm-objcopy. Update a test case so a section has different physical and virtual addresses. Fixes B35708 Authored By: Owen Shaw (owenpshaw) Differential Revision: https://reviews.llvm.org/D41619 llvm-svn: 323144
Diffstat (limited to 'libcxx/include/algorithm')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud