summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/functionalities/completion/TestCompletion.py
diff options
context:
space:
mode:
authorFangrui Song <maskray@google.com>2019-08-20 08:34:56 +0000
committerFangrui Song <maskray@google.com>2019-08-20 08:34:56 +0000
commitf66b767abe5edcdd7ab4a25007b71437f58c1369 (patch)
treea0b86dd687bf179ddf4a51b0c8439b3cf7c63c09 /lldb/packages/Python/lldbsuite/test/functionalities/completion/TestCompletion.py
parent01c7f4b6066935c5bd6f844fdb1d419c568aef14 (diff)
downloadbcm5719-llvm-f66b767abe5edcdd7ab4a25007b71437f58c1369.tar.gz
bcm5719-llvm-f66b767abe5edcdd7ab4a25007b71437f58c1369.zip
[ELF][AArch64] Allow PT_LOAD to have overlapping p_offset ranges
Ported the D64906 technique to AArch64. It deletes 3 alignments at PT_LOAD boundaries for the default case: the size of an aarch64 binary decreases by at most 192kb. If `sh_addralign(.tdata) < sh_addralign(.tbss)`, we can potentially make `p_vaddr(PT_TLS)%p_align(PT_TLS) != 0`. ld.so that are known to have problems if p_vaddr%p_align!=0: * musl<=1.1.22 * FreeBSD 13.0-CURRENT (and before) rtld-elf arm64 New test aarch64-tls-vaddr-align.s checks that our workaround makes p_vaddr%p_align = 0. Reviewed By: ruiu Differential Revision: https://reviews.llvm.org/D64930 llvm-svn: 369344
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/functionalities/completion/TestCompletion.py')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud