Remove dict_empty/mdict_empty
These functions are not used in the code base, remove them. gdb/ChangeLog: * dictionary.c (dict_empty, mdict_empty): Remove. * dictionary.c (mdict_empty): Remove. Change-Id: I4c1b08c730f6790b2f3d28b680607618e3c08e48
This commit is contained in:
parent
cb8c24b661
commit
b62f6f5435
|
@ -1,3 +1,8 @@
|
|||
2019-11-26 Simon Marchi <simon.marchi@efficios.com>
|
||||
|
||||
* dictionary.c (dict_empty, mdict_empty): Remove.
|
||||
* dictionary.c (mdict_empty): Remove.
|
||||
|
||||
2019-11-26 Simon Marchi <simon.marchi@efficios.com>
|
||||
|
||||
* arc-tdep.c (arc_insn_get_memory_base_reg): Make static.
|
||||
|
|
|
@ -508,16 +508,6 @@ dict_size (const struct dictionary *dict)
|
|||
implemented generically by means of the vtable. Typically, they're
|
||||
rarely used. */
|
||||
|
||||
/* Test to see if DICT is empty. */
|
||||
|
||||
static int
|
||||
dict_empty (struct dictionary *dict)
|
||||
{
|
||||
struct dict_iterator iter;
|
||||
|
||||
return (dict_iterator_first (dict, &iter) == NULL);
|
||||
}
|
||||
|
||||
|
||||
/* The functions implementing the dictionary interface. */
|
||||
|
||||
|
@ -1283,17 +1273,3 @@ mdict_size (const struct multidictionary *mdict)
|
|||
|
||||
return size;
|
||||
}
|
||||
|
||||
/* See dictionary.h. */
|
||||
|
||||
bool
|
||||
mdict_empty (const struct multidictionary *mdict)
|
||||
{
|
||||
for (unsigned short idx = 0; idx < mdict->n_allocated_dictionaries; ++idx)
|
||||
{
|
||||
if (!dict_empty (mdict->dictionaries[idx]))
|
||||
return false;
|
||||
}
|
||||
|
||||
return true;
|
||||
}
|
||||
|
|
|
@ -93,10 +93,6 @@ extern void mdict_add_symbol (struct multidictionary *mdict,
|
|||
extern void mdict_add_pending (struct multidictionary *mdict,
|
||||
const struct pending *symbol_list);
|
||||
|
||||
/* Is the multidictionary empty? */
|
||||
|
||||
extern int mdict_empty (struct multidictionary *mdict);
|
||||
|
||||
/* A type containing data that is used when iterating over all symbols
|
||||
in a dictionary. Don't ever look at its innards; this type would
|
||||
be opaque if we didn't need to be able to allocate it on the
|
||||
|
|
Loading…
Reference in New Issue