llvm-6502/test/MC/MachO/AArch64
Rafael Espindola a23cc6a1ea 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
2015-01-19 21:11:14 +00:00
..
cfstring.s Add a test that would have found the issue with r225644. 2015-01-14 20:24:46 +00:00
darwin-ARM64-local-label-diff.s
darwin-ARM64-reloc.s Add a test for the recent compiler-rt build failure. 2014-12-31 16:58:05 +00:00
lit.local.cfg
mergeable.s Add r224985 back with fixes. 2015-01-19 21:11:14 +00:00
reloc-crash2.s Add a test that would have found the issue in r224935. 2015-01-07 21:10:25 +00:00
reloc-crash.s Add a testcase that would have found the problem in r225048. 2015-01-06 01:41:24 +00:00