diff options
author | Andrew Burgess <aburgess@redhat.com> | 2021-11-24 11:15:55 +0000 |
---|---|---|
committer | Andrew Burgess <aburgess@redhat.com> | 2021-11-25 09:54:58 +0000 |
commit | 0c1e6e265b276542ccb3f392c3070c3dd9339303 (patch) | |
tree | 3b45413e28d99ab95b068db30e0365c6c9ebc5ad /gdb/target.h | |
parent | eec685f8a6e1a654bb82b0f20134689861589866 (diff) | |
download | fsf-binutils-gdb-0c1e6e265b276542ccb3f392c3070c3dd9339303.zip fsf-binutils-gdb-0c1e6e265b276542ccb3f392c3070c3dd9339303.tar.gz fsf-binutils-gdb-0c1e6e265b276542ccb3f392c3070c3dd9339303.tar.bz2 |
gdb: introduce a new overload of target_can_async_p
There are a few places where we call the target_ops::can_async_p
member function directly, instead of using the target_can_async_p
wrapper.
In some of these places this is because we need to ask before the
target has been pushed, and in another location (in target.c) it seems
unnecessary to go through the wrapper when we are already in target.c
code.
However, in the next commit I'd like to hoist some common checks out
of target specific code into target.c. To achieve this, in this
commit, I introduce a new overload of target_can_async_p which takes a
target_ops pointer, and calls the ::can_async_p method directly. I
then make use of the new overload where appropriate.
There should be no user visible changes after this commit.
Diffstat (limited to 'gdb/target.h')
-rw-r--r-- | gdb/target.h | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/gdb/target.h b/gdb/target.h index 4dc17fd..e709b7d 100644 --- a/gdb/target.h +++ b/gdb/target.h @@ -1886,6 +1886,10 @@ extern bool target_async_permitted; /* Can the target support asynchronous execution? */ extern bool target_can_async_p (); +/* An overload of the above that can be called when the target is not yet + pushed, this calls TARGET::can_async_p directly. */ +extern bool target_can_async_p (struct target_ops *target); + /* Is the target in asynchronous execution mode? */ extern bool target_is_async_p (); |