gdb/mep: Use default gdbarch methods where possible
authorAndrew Burgess <andrew.burgess@embecosm.com>
Thu, 10 Jan 2019 18:37:03 +0000 (18:37 +0000)
committerAndrew Burgess <andrew.burgess@embecosm.com>
Tue, 23 Apr 2019 21:50:23 +0000 (22:50 +0100)
commit8e2b5aea9d3f16961f7fac15caec00e955c1dc81
tree32d8554c6838ba31b28622b647a841683c00a2ba
parent43cf3eded2d3ec0af6f5cf534dd89f47d4958a92
gdb/mep: 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:

* mep-tdep.c (mep_unwind_pc): Delete.
(mep_unwind_sp): Delete.
(mep_dummy_id): Delete.
(mep_gdbarch_init): Don't register deleted functions with
gdbarch.
gdb/ChangeLog
gdb/mep-tdep.c