[lld] r229072 - ELF/AArch64: Add support for checking for ABS32 overflow

[Will Newton]

On 17 February 2015 at 00:46, Filipe Cabecinhas <filcab at gmail.com> wrote:

Hi Filipe,

> Here's our output for that test (it seems like it has the wrong order (data1
> vs data2)):
>
> ----------------------------
> C:\Buildbot\Slave\builds\1.LLVM.Windows.Phase.2\llvm.obj\bin>not lld -flavor
> gnu -target arm64 -o
> C:\Buildbot\Slave\builds\1.LLVM.Windows.Phase.2\llvm.obj\tools\lld\test\elf\AArch64\Output\rel-abs32-overflow.test.tmp-exe
> C:\Buildbot\Slave\builds\1.LLVM.Windows.Phase.2\llvm.obj\tools\lld\test\elf\AArch64\Output\rel-abs32-overflow.test.tmp-obj
> 2>&1
> Relocation out of range in file
> C:\Buildbot\Slave\builds\1.LLVM.Windows.Phase.2\llvm.obj\tools\lld\test\elf\AArch64\Output\rel-abs32-overflow.test.tmp-obj:
> reference from data2+0 to data1+34359738369 of type 258 (R_AARCH64_ABS32)
> Relocation out of range in file
> C:\Buildbot\Slave\builds\1.LLVM.Windows.Phase.2\llvm.obj\tools\lld\test\elf\AArch64\Output\rel-abs32-overflow.test.tmp-obj:
> reference from data1+0 to data2+34359738369 of type 258 (R_AARCH64_ABS32)
> LLVM ERROR: relocating output
> ---------------------------------

Thanks for that. I've checked in a fix (use CHECK-DAG instead of
CHECK) which should hopefully fix the problem. Let me know if it works
for you.

-- 
Will Newton
Toolchain Working Group, Linaro