summaryrefslogtreecommitdiff
path: root/bindings
diff options
context:
space:
mode:
authorRafael Espindola <rafael.espindola@gmail.com>2015-01-19 21:11:14 +0000
committerRafael Espindola <rafael.espindola@gmail.com>2015-01-19 21:11:14 +0000
commita23cc6a1ea64d1eeaf61ca45881b61036f414913 (patch)
treed2a84af0d47f71f61205f907c716e111af631546 /bindings
parenta7852bfa47b9e907b50eaaa5ce4e1c79e1d5150b (diff)
Add r224985 back with fixes.
The fixes are to note that AArch64 has additional restrictions on when local relocations can be used. In particular, ld64 requires that relocations to cstring/cfstrings use linker visible symbols. Original message: In an assembly expression like bar: .long L0 + 1 the intended semantics is that bar will contain a pointer one byte past L0. In sections that are merged by content (strings, 4 byte constants, etc), a single position in the section doesn't give the linker enough information. For example, it would not be able to tell a relocation must point to the end of a string, since that would look just like the start of the next. The solution used in ELF to use relocation with symbols if there is a non-zero addend. In MachO before this patch we would just keep all symbols in some sections. This would miss some cases (only cstrings on x86_64 were implemented) and was inefficient since most relocations have an addend of 0 and can be represented without the symbol. This patch implements the non-zero addend logic for MachO too. git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@226503 91177308-0d34-0410-b5e6-96231b3b80d8
Diffstat (limited to 'bindings')
0 files changed, 0 insertions, 0 deletions