This is the mail archive of the binutils@sources.redhat.com mailing list for the binutils project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
Hi all,Hmm, yes, two occurances of the same problem definitly suggests the current technique isn't maintainable.
I bump with same problem on h8300 arches, and for solving this problem one and for all, I see next 2 ways:
1) export from archures.c something likeThere is bfd_arch_list(). A per-architecture one would do what GDB needs. See gdbarch.c:gdbarch_printable_names().
const bfd_arch_info_type *bfd_get_lookup_arch_head
(enum bfd_architecture arch);
This is not so good, because it assume hacking bfd internals.
2) Or, put gdbarch_printables_names to bfd like:
const char **bfd_machine_printables_names (enum bfd_architecture arch);
which return all machine names for given architecture. What do you think?
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |