diff options
| author | James Greenhalgh <james.greenhalgh@arm.com> | 2017-10-26 11:30:40 +0100 |
|---|---|---|
| committer | Nick Clifton <nickc@redhat.com> | 2017-10-26 11:30:40 +0100 |
| commit | 4062f504eba4835579bcc360e9eff3e7d92f5a6c (patch) | |
| tree | 16890cccb992de750ef8df12a4b00361155cfa5c /gdb/breakpoint.c | |
| parent | 6abc18bbbf03dc4aee0b0f2cd851d9bc9a983e20 (diff) | |
| download | binutils-4062f504eba4835579bcc360e9eff3e7d92f5a6c.zip binutils-4062f504eba4835579bcc360e9eff3e7d92f5a6c.tar.gz binutils-4062f504eba4835579bcc360e9eff3e7d92f5a6c.tar.bz2 | |
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.
Diffstat (limited to 'gdb/breakpoint.c')
0 files changed, 0 insertions, 0 deletions