gdb/tilegx: Use default gdbarch methods where possible
authorAndrew Burgess <andrew.burgess@embecosm.com>
Thu, 10 Jan 2019 20:25:59 +0000 (20:25 +0000)
committerAndrew Burgess <andrew.burgess@embecosm.com>
Tue, 23 Apr 2019 22:06:53 +0000 (23:06 +0100)
commit0f534d767b257fffd8a9b231c97ff9ed33688452
tree60c2b4fa445a09b49e9aa2f9954161382b17e497
parent1ba7b7f9384eafc0748cee4c6731d6bdb717bd20
gdb/tilegx: Use default gdbarch methods where possible

Make use of the default gdbarch methods for gdbarch_dummy_id,
gdbarch_unwind_pc, and gdbarch_unwind_sp where possible.

I have not tested this change but, by inspecting the code, I believe
the default methods are equivalent to the code being deleted.

gdb/ChangeLog:

* tilegx-tdep.c (tilegx_unwind_sp): Delete.
(tilegx_unwind_pc): Delete.
(tilegx_unwind_dummy_id): Delete.
(tilegx_gdbarch_init): Don't register deleted functions with
gdbarch.
gdb/ChangeLog
gdb/tilegx-tdep.c