gdb/ft32: Use default gdbarch methods where possible
authorAndrew Burgess <andrew.burgess@embecosm.com>
Wed, 19 Dec 2018 22:34:19 +0000 (22:34 +0000)
committerAndrew Burgess <andrew.burgess@embecosm.com>
Wed, 27 Feb 2019 14:54:44 +0000 (16:54 +0200)
commit68b867f30eeca7e9585e9ee16e824f5a18e2bc6c
tree833e90a3babdf2660baff9f719de2fa29ba80db3
parent2fbe7ad059d9ec2a8a378a5c2b973a1188677422
gdb/ft32: 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/ft32-tdep.c (ft32_dummy_id): Delete.
(ft32_unwind_pc): Delete.
(ft32_unwind_sp): Delete.
(ft32_gdbarch_init): Don't register deleted functions with
gdbarch.
gdb/ChangeLog
gdb/ft32-tdep.c