aboutsummaryrefslogtreecommitdiff
path: root/gdb/source-cache.c
diff options
context:
space:
mode:
authorTankut Baris Aktemur <tankut.baris.aktemur@intel.com>2020-04-02 15:11:22 +0200
committerTankut Baris Aktemur <tankut.baris.aktemur@intel.com>2020-04-02 15:11:22 +0200
commita5863204fb1b9c03627edc3bb447c5958ef96458 (patch)
treec80edf717564f8ac3da1e8202d0e56f06271265f /gdb/source-cache.c
parent4b27d27c07a9514d5f6d0876f659a32378fb4801 (diff)
downloadgdb-a5863204fb1b9c03627edc3bb447c5958ef96458.zip
gdb-a5863204fb1b9c03627edc3bb447c5958ef96458.tar.gz
gdb-a5863204fb1b9c03627edc3bb447c5958ef96458.tar.bz2
gdbserver: make linux target op 'cannot_store_register' a predicate function
The comment for the linux target op 'cannot_store_register' states the following: /* Returns 0 if we can store the register, 1 if we can not store the register, and 2 if failure to store the register is acceptable. */ There is only one low target, linux-ppc-low, that potentially returns 2. There are two places that call the 'cannot_store_register' target op in linux-low.cc. None of these locations distinguish a '2' from a '1'. Hence, to simplify the definition, make the function a predicate that returns either 0 or 1. This is also consistent with the companion function, 'cannot_fetch_register'. gdbserver/ChangeLog: 2020-04-02 Tankut Baris Aktemur <tankut.baris.aktemur@intel.com> * linux-low.h (struct linux_target_ops): Update the comment for 'cannot_store_register' to return 0 or 1. * linux-ppc-low.cc (ppc_cannot_store_register): Return 1 instead of 2.
Diffstat (limited to 'gdb/source-cache.c')
0 files changed, 0 insertions, 0 deletions