From 1913360a168b8cae186e224620294801dd770318 Mon Sep 17 00:00:00 2001 From: Martin Storsjo Date: Tue, 25 Jul 2017 19:57:26 +0000 Subject: [PATCH] [AArch64] Update a comment in a test The comment ended up outdated when the test was rewritten in SVN r192281. Differential Revision: https://reviews.llvm.org/D35543 llvm-svn: 309016 --- llvm/test/MC/AArch64/adrp-relocation.s | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/llvm/test/MC/AArch64/adrp-relocation.s b/llvm/test/MC/AArch64/adrp-relocation.s index 9a809cf..474a1ee 100644 --- a/llvm/test/MC/AArch64/adrp-relocation.s +++ b/llvm/test/MC/AArch64/adrp-relocation.s @@ -2,11 +2,10 @@ // RUN: llvm-mc -target-abi=ilp32 -triple=aarch64-linux-gnu -filetype=obj \ // RUN: -o - %s| llvm-readobj -r - | FileCheck -check-prefix=CHECK-ILP32 %s .text -// These should produce an ADRP/ADD pair to calculate the address of -// testfn. The important point is that LLVM shouldn't think it can deal with the -// relocation on the ADRP itself (even though it knows everything about the -// relative offsets of testfn and foo) because its value depends on where this -// object file's .text section gets relocated in memory. +// This tests that LLVM doesn't think it can deal with the relocation on the ADRP +// itself (even though it knows everything about the relative offsets of sym and +// the adrp instruction) because its value depends on where this object file's +// .text section gets relocated in memory. adrp x0, sym adrp x0, :got:sym adrp x0, :gottprel:sym -- 2.7.4