gdb/cris: Use default gdbarch methods where possible
authorAndrew Burgess <andrew.burgess@embecosm.com>
Sun, 9 Sep 2018 16:17:05 +0000 (17:17 +0100)
committerAndrew Burgess <andrew.burgess@embecosm.com>
Wed, 27 Feb 2019 14:54:43 +0000 (16:54 +0200)
commit8010f576414759bf5bdcfeaa64226bf03586b763
treec0f07c3fe031227ca0d3b76b1d45941cb2d7e6b5
parentb56bf084434de08080875134e983f8b46eb2328f
gdb/cris: 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:

* gdb/cris-tdep.c (cris_dummy_id): Delete.
(cris_unwind_pc): Delete.
(cris_unwind_sp): Delete.
(cris_gdbarch_init): Don't register deleted functions with
gdbarch.
gdb/ChangeLog
gdb/cris-tdep.c