This is the mail archive of the
mailing list for the GDB project.
Re: objdump -M for x86
- To: Andrew Cagney <ac131313 at cygnus dot com>
- Subject: Re: objdump -M for x86
- From: Alan Modra <amodra at bigpond dot net dot au>
- Date: Wed, 14 Nov 2001 17:43:50 +1030
- Cc: binutils at sources dot redhat dot com, gdb at sources dot redhat dot com
- References: <20011114134429.G6922@bubble.sa.bigpond.net.au> <3BF200F9.firstname.lastname@example.org>
On Wed, Nov 14, 2001 at 12:28:25AM -0500, Andrew Cagney wrote:
> > Applying to mainline. Note to gdb people: Some backwards compatibility
> > stuff can be removed when i386-tdep.c and x86-64-tdep are updated to use
> > the new (old!) print_insn_i386.
> Hmm, I was wondering what you were talking about until I found this:
Actually, I was meaning that you don't need to call print_insn_i386_att
or ..._intel; Just call print_insn_i386 with info->mach set.
Well, x86_64 follows the name used by -m
> Next problem ... If I understand things correctly, the set of possible
> options, for a given ISA family, is finite. Could that finite list be
> made available via a published interface?
Yes, good idea. Something like:
const char **opcodes_disasm_options (enum bfd_architecture arch)
returning a malloc'd list of strings for the given arch?