gdb/m32r: Use default gdbarch methods where possible
authorAndrew Burgess <andrew.burgess@embecosm.com>
Thu, 10 Jan 2019 18:29:47 +0000 (18:29 +0000)
committerAndrew Burgess <andrew.burgess@embecosm.com>
Tue, 23 Apr 2019 21:50:21 +0000 (22:50 +0100)
commit5e79b7bb69c797c3ca401cfa0f7a616eb2e3efe8
treed9f640d446f9f0762754ea50acdababb470d4c67
parent89b268d8233e11acdfbc5af196166aacc1440ff3
gdb/m32r: 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:

* m32r-tdep.c (m32r_unwind_sp): Delete.
(m32r_unwind_pc): Delete.
(m32r_dummy_id): Delete.
(m32r_gdbarch_init): Don't register deleted functions with
gdbarch.
gdb/ChangeLog
gdb/m32r-tdep.c