gdb/lm32: Use default gdbarch methods where possible
authorAndrew Burgess <andrew.burgess@embecosm.com>
Thu, 10 Jan 2019 18:21:40 +0000 (18:21 +0000)
committerAndrew Burgess <andrew.burgess@embecosm.com>
Tue, 23 Apr 2019 21:50:20 +0000 (22:50 +0100)
commit946c28d2f93789ff4eec86a8c321af35759fa20a
treea5d32de4dcaeb262b9d5d4fc039957ad1735cf15
parentbf12844a68f3f4f267846a19df6a280f53e7ec5f
gdb/lm32: 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/lm32-tdep.c (lm32_unwind_sp): Delete.
(lm32_unwind_pc): Delete.
(lm32_dummy_id): Delete.
(lm32_gdbarch_init): Don't register deleted functions with
gdbarch.
gdb/ChangeLog
gdb/lm32-tdep.c