Fix aarch64 ftrace JIT condition testcase
authorAntoine Tremblay <antoine.tremblay@ericsson.com>
Wed, 13 Apr 2016 13:40:00 +0000 (09:40 -0400)
committerAntoine Tremblay <antoine.tremblay@ericsson.com>
Wed, 13 Apr 2016 13:40:00 +0000 (09:40 -0400)
commit45e3745ed0e034fdec5beee0738f383bd6e2e045
treed7958eb9c9c8ce9a0b2d3ce8063eca1d76d2c52b
parent3a00c80277a54abe0b286a6e8babc8fe50120205
Fix aarch64 ftrace JIT condition testcase

This patch fixes the following failure:
FAIL: gdb.trace/trace-condition.exp: ftrace: -(21 << 1) == -42: check 10
frames were collected.

This was due to aarch64_emit_sub using the wrong order in its operands, so the
operation would end up being 42 - 0 rather than 0 - 42.

This patch also fixes the order of aarch64_emit_add for clarity.

The test case for emit_sub is fixed so that the proper order of
the operands is needed for the test to pass.

Tested on aarch64-native-extended-gdbserver.

Note: trace-condition.exp was broken a bit so I had to modify it to run
the test. A fix is coming for that in another patch.

gdb/gdbserver/ChangeLog:

* linux-aarch64-low.c (aarch64_emit_add): Switch x1 and x0.
(aarch64_emit_sub): Likewise.

gdb/testsuite/ChangeLog:

* gdb.trace/trace-condition.exp (foreach): Fix emit_sub testcase.
gdb/gdbserver/ChangeLog
gdb/gdbserver/linux-aarch64-low.c
gdb/testsuite/ChangeLog
gdb/testsuite/gdb.trace/trace-condition.exp
This page took 0.025233 seconds and 4 git commands to generate.