gdb/m32c: Use default gdbarch methods where possible
authorAndrew Burgess <andrew.burgess@embecosm.com>
Thu, 10 Jan 2019 18:27:12 +0000 (18:27 +0000)
committerAndrew Burgess <andrew.burgess@embecosm.com>
Tue, 23 Apr 2019 21:50:21 +0000 (22:50 +0100)
commit89b268d8233e11acdfbc5af196166aacc1440ff3
treeef5eeadd7fb556d5e96be9a571232fc1bffd1f04
parent946c28d2f93789ff4eec86a8c321af35759fa20a
gdb/m32c: 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:

* m32c-tdep.c (m32c_unwind_pc): Delete.
(m32c_unwind_sp): Delete.
(m32c_dummy_id): Delete.
(m32c_gdbarch_init): Don't register deleted functions with
gdbarch.
gdb/ChangeLog
gdb/m32c-tdep.c