gdb/or1k: Use default gdbarch methods where possible
authorAndrew Burgess <andrew.burgess@embecosm.com>
Thu, 10 Jan 2019 18:58:18 +0000 (18:58 +0000)
committerAndrew Burgess <andrew.burgess@embecosm.com>
Tue, 23 Apr 2019 21:50:26 +0000 (22:50 +0100)
commit3f2cef4945a916e3b566010340bbc70cfe927916
tree259b8ca5cf03f9a9e37380eda7932d9b0dd362e2
parent96acf8844a655e34de3f3b014a7f64f26266dee1
gdb/or1k: Use default gdbarch methods where possible

Make use of the default gdbarch method gdbarch_dummy_id 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.

This commit leaves or1k_unwind_sp and or1k_unwind_pc in place.  These
functions do match the default methods except that they add additional
debugging code.  In order to preserve the debug I have left these
functions unchanged.

gdb/ChangeLog:

* or1k-tdep.c (or1k_dummy_id): Delete.
(or1k_gdbarch_init): Don't register deleted function with gdbarch.
gdb/ChangeLog
gdb/or1k-tdep.c