gdb/msp430: Use default gdbarch methods where possible
authorAndrew Burgess <andrew.burgess@embecosm.com>
Thu, 10 Jan 2019 18:51:11 +0000 (18:51 +0000)
committerAndrew Burgess <andrew.burgess@embecosm.com>
Tue, 23 Apr 2019 21:50:24 +0000 (22:50 +0100)
commitc825904428f7c89a65eeb313b243f65e950a0a19
treea03c2b27d7c6f44c0921cbee9a7d05600ac669c2
parent27f113c8e9b2361caf3dfcf15437020306bf93b9
gdb/msp430: 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:

* msp430-tdep.c (msp430_unwind_pc): Delete.
(msp430_unwind_sp): Delete.
(msp430_dummy_id): Delete.
(msp430_gdbarch_init): Don't register deleted functions with
gdbarch.
gdb/ChangeLog
gdb/msp430-tdep.c