diff options
| author | Andrew Burgess <aburgess@redhat.com> | 2022-08-11 12:43:08 +0100 |
|---|---|---|
| committer | Andrew Burgess <aburgess@redhat.com> | 2022-08-31 16:07:05 +0100 |
| commit | b49d7aa74466fb73529ebf0e6c907c2142505610 (patch) | |
| tree | 4dd5a8cb2bb7725b23d07b8680623fe4811c2088 /gdb/target-descriptions.h | |
| parent | 3095d92634a938d447eed1ef2c5d59f40f44078e (diff) | |
| download | binutils-gdb-b49d7aa74466fb73529ebf0e6c907c2142505610.tar.gz | |
gdb: Add tdesc_found_register function to tdesc API
This commit adds a new function to the target description API within
GDB. This new function is not used in this commit, but will be used
in the next commit, I'm splitting it out into a separate patch for
easier review.
What I want to do in the next commit is check to see if a target
description supplied a particular register, however, the register in
question could appear in one of two possible features.
The new function allows me to ask the tdesc_arch_data whether a
register was found and assigned a particular GDB register number once
all of the features have been checked. I think this is a much simpler
solution than adding code such that, while checking each feature, I
spot if the register I'm processing is the one I care about.
No tests here as the new code is not used, but this code will be
exercised in the next commit.
Diffstat (limited to 'gdb/target-descriptions.h')
| -rw-r--r-- | gdb/target-descriptions.h | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/gdb/target-descriptions.h b/gdb/target-descriptions.h index 3b90dedcd80..3ab0ae2542d 100644 --- a/gdb/target-descriptions.h +++ b/gdb/target-descriptions.h @@ -170,6 +170,10 @@ int tdesc_numbered_register_choices (const struct tdesc_feature *feature, struct tdesc_arch_data *data, int regno, const char *const names[]); +/* Return true if DATA contains an entry for REGNO, a GDB register + number. */ + +extern bool tdesc_found_register (struct tdesc_arch_data *data, int regno); /* Accessors for target descriptions. */ |