As Alan predicted at https://sourceware.org/ml/binutils/2017-10/msg00137.html the...
authorJames Greenhalgh <james.greenhalgh@arm.com>
Thu, 26 Oct 2017 10:30:40 +0000 (11:30 +0100)
committerNick Clifton <nickc@redhat.com>
Thu, 26 Oct 2017 10:30:40 +0000 (11:30 +0100)
commit4062f504eba4835579bcc360e9eff3e7d92f5a6c
tree16890cccb992de750ef8df12a4b00361155cfa5c
parent6abc18bbbf03dc4aee0b0f2cd851d9bc9a983e20
As Alan predicted at https://sourceware.org/ml/binutils/2017-10/msg00137.html the values in some Arm tests need updating after recent changes. These looked a bit spooky at first, but they are just a difference in the order we emit veneers and far jumps, so are not so scary after all.

Checked with an arm-none-eabi tester and an arm-none-linux-gnueabi tester with no issues.

* testsuite/ld-arm/cortex-a8-far.d: Update expected disassembly.
* testsuite/ld-arm/farcall-group-size2: Likewise.
* testsuite/ld-arm/farcall-group.d: Likewise.
ld/ChangeLog
ld/testsuite/ld-arm/cortex-a8-far.d
ld/testsuite/ld-arm/farcall-group-size2.d
ld/testsuite/ld-arm/farcall-group.d